This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-19990321 bootstrap failure on DUNIX
- To: Stefan Schwarzer <sts at ica1 dot uni-stuttgart dot de>
- Subject: Re: egcs-19990321 bootstrap failure on DUNIX
- From: Jeffrey A Law <law at upchuck dot cygnus dot com>
- Date: Fri, 09 Apr 1999 04:45:47 -0600
- cc: egcs-bugs at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <199903221558.QAA07148@cougar.ica1.uni-stuttgart.de>you write:
>
> On DUNIX 4.0C [OSF1 cougar.ica1.uni-stuttgart.de V4.0 564.32 alpha]
> bootstrapping the egcs-19990321 after configure with the only option
> --prefix=/local/egcs-snapshot
> fails with the following error - here with some context:
[ ... ]
> stage1/xgcc -Bstage1/ -B/local/egcs-snapshot/alphaev56-dec-osf4.0c/bin/ -D
> IN_GCC -DHAIFA -W -Wall -O2 -g -O2 -DHAVE_CONFIG_H -I. -I../../gcc -
> I../../gcc/config -I../../gcc/../include \
> -DTARGET_MACHINE=\"alphaev56-dec-osf4.0c\" -DUSE_COLLECT2 \
> -c `echo ../../gcc/collect2.c | sed 's,^\./,,'`
> In file included from /usr/include/obj.h:91,
> from include/ldfcn.h:54,
> from ../../gcc/collect2.c:98:
> include/elf_abi.h:433: unterminated string or character constant
> include/elf_abi.h:433: possible real start of unterminated constant
> include/elf_abi.h:44: unterminated `#if' conditional
> In file included from /usr/include/elf_mips.h:46,
> from /usr/include/obj.h:92,
> from include/ldfcn.h:54,
> from ../../gcc/collect2.c:98:
> include/elf_abi.h:433: unterminated string or character constant
> include/elf_abi.h:433: possible real start of unterminated constant
> include/elf_abi.h:44: unterminated `#if' conditional
> In file included from /usr/include/obj_ext.h:15,
> from /usr/include/obj_type.h:46,
> from /usr/include/obj.h:96,
> from include/ldfcn.h:54,
> from ../../gcc/collect2.c:98:
> include/elf_abi.h:433: unterminated string or character constant
> include/elf_abi.h:433: possible real start of unterminated constant
> include/elf_abi.h:44: unterminated `#if' conditional
This was a bug in the fast-fixincludes support and I believe has been fixed.
Thanks,
jeff