public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Corrin Lakeland <lakeland@cs.otago.ac.nz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/7210: bootstrap fails on darwin Date: Fri, 05 Jul 2002 19:06:00 -0000 [thread overview] Message-ID: <20020706020602.21700.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/7210; it has been noted by GNATS. From: Corrin Lakeland <lakeland@cs.otago.ac.nz> To: Devang Patel <dpatel@apple.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/7210: bootstrap fails on darwin Date: Sat, 6 Jul 2002 14:01:47 +1200 (NZST) On Fri, 5 Jul 2002, Devang Patel wrote: > Try using "CC=cc -no-cpp-precomp" Unfortunatly I'm already doing that, here is the exact error: gcc -no-cpp-precomp -c -DIN_GCC -g -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedan tic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I. -I./. -I./config -I./../include cppinit.c -o cppinit.o In file included from cppinit.c:23: system.h:331: warning: ANSI C forbids const or volatile functions In file included from system.h:490, from cppinit.c:23: ../include/libiberty.h:86: warning: ANSI C forbids const or volatile functions ../include/libiberty.h:158: warning: ANSI C forbids const or volatile functions ../include/libiberty.h:168: warning: ANSI C forbids const or volatile functions ../include/libiberty.h:193: warning: ANSI C forbids const or volatile functions In file included from cpplib.h:28, from cppinit.c:24: line-map.h:89: warning: ANSI C forbids const or volatile functions line-map.h:94: warning: ANSI C forbids const or volatile functions In file included from cppinit.c:24: cpplib.h:508: warning: ANSI C forbids const or volatile functions cpplib.h:535: warning: ANSI C forbids const or volatile functions cpplib.h:564: warning: ANSI C forbids const or volatile functions cpplib.h:566: warning: ANSI C forbids const or volatile functions cpplib.h:681: warning: ANSI C forbids const or volatile functions In file included from cppinit.c:25: cpphash.h:479: warning: ANSI C forbids const or volatile functions cpphash.h:506: warning: ANSI C forbids const or volatile functions cppinit.c:150: parse error before `,' cppinit.c:150: parse error before `,' cppinit.c:150: parse error before `,' cppinit.c:151: parse error before `,' cppinit.c:151: parse error before `,' cppinit.c:151: parse error before `,' cppinit.c:152: parse error before `,' cppinit.c:152: parse error before `,' cppinit.c:152: parse error before `,' cppinit.c:898: warning: ANSI C forbids const or volatile functions make[1]: *** [cppinit.o] Error 1 make[1]: Leaving directory `/Users/lakeland/src/gcc/gcc' oucs581 ~/src/gcc % cc -v -v Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs Apple Computer, Inc. version gcc-934.3, based on gcc version 2.95.2 19991024 (release) Anything else I can provide? Corrin > > On Thursday, July 4, 2002, at 01:31 PM, lakeland@acm.org wrote: > > > > >> Number: 7210 > >> Category: bootstrap > >> Synopsis: bootstrap fails on darwin > >> Confidential: no > >> Severity: serious > >> Priority: medium > >> Responsible: unassigned > >> State: open > >> Class: sw-bug > >> Submitter-Id: net > >> Arrival-Date: Thu Jul 04 13:36:00 PDT 2002 > >> Closed-Date: > >> Last-Modified: > >> Originator: Corrin Lakeland > >> Release: Head > >> Organization: > >> Environment: > > ppc-apple-darwin5.4 (+ most gnu tools) > >> Description: > > bootstrap fails on darwin due to errors in darwin's built > > in CC. > > > > cppinit.c:150: parse error before `,' > > cppinit.c:150: parse error before `,' > > cppinit.c:150: parse error before `,' > > > > The problem isn't with the tricky #define, but with the > > preallocation of static arrays. It seems darwin's CC > > (modified GCC 2.95.2) cannot parse declare & initialise. > >> How-To-Repeat: > > ./configure, make > >> Fix: > > Allocate the static arrays differently, or wait until gcc3 is standard > > on darwin and ignore the problem. > > > > Fixing the first file is fairly easy but it gets tedious > > after that. Using make -k I managed to get it down to > > three files that needed fixing although fixing them might > > have brought up more problems. > >> Release-Note: > >> Audit-Trail: > >> Unformatted: > > >
next reply other threads:[~2002-07-06 2:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-05 19:06 Corrin Lakeland [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-06 14:36 Wolfgang Bangerth 2003-05-06 14:32 bangerth 2003-05-01 17:36 Andreas Tobler 2002-07-05 18:26 Devang Patel 2002-07-04 13:36 lakeland
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020706020602.21700.qmail@sources.redhat.com \ --to=lakeland@cs.otago.ac.nz \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).