This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
BUG in egcs 1.1.2 under glibc 2.1.1
- To: egcs-bugs at egcs dot cygnus dot com
- Subject: BUG in egcs 1.1.2 under glibc 2.1.1
- From: Andreas Hartmann <andihartmann at 01019freenet dot de>
- Date: Fri, 18 Jun 1999 17:11:24 +0200
- Reply-To: andihartmann at 01019freenet dot de
Hallo!
I probably found a bug in compiling
egcs 2.91.66 19990314 on a i586-pc-linux-gnu.
The options I used to compile:
configure --enable-shared --enable-threads --prefix=/usr
make
The following describes the situation the bug occured:
make[1]: Entering directory `/usr/temp/egcs-1.1.2-cpp/compile/gcc'
rm -f SYSCALLS.c tmp-SYSCALLS.s
cat ../../gcc/sys-types.h ../../gcc/sys-protos.h > SYSCALLS.c
/temp/egcs-1.1.2-cpp/compile/gcc/xgcc
-B/temp/egcs-1.1.2-cpp/compile/gcc/ -DIN_GCC -g -O2 -I./include
-I. -I../../gcc -I../../gcc/config \
-aux-info SYSCALLS.c.X -S -o tmp-SYSCALLS.s SYSCALLS.c
xgcc: Internal compiler error: program cpp got fatal signal 11
make[1]: *** [SYSCALLS.c.X] Error 1
make[1]: Leaving directory `/usr/temp/egcs-1.1.2-cpp/compile/gcc'
make: *** [all-gcc] Error 2
I read, that signal 11 could be a result of buggy hardware. But I donīt
think so, because there is absolutely no trouble compiling with running
glibc
2.0.7. Always I compile egcs itself, running glibc 2.1.1, I got the
mentioned errormessage (at the very same position). Interesting too:
compiling egcs-1.1.1 produces at the same position with glibc2.1.1 the
same error. Strange, isnīt it?!
I would be glad, if you could tell me a workaround or a solution,
because I wonīt miss glibc 2.1.1, because itīs a very fast glibc!
Thanks for your work and kind regards,
A. Hartmann