Re: bootstrap/7210: bootstrap fails on darwin

[Corrin Lakeland <lakeland at cs dot otago dot ac dot nz>]

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:
 > >
 >