gcc/g++ seriously broken in gutsy latest amd64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-4.1 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gcc-4.1
I've been trying to build some stuff today, and while basic hello world apps compile and run, more complicated things invariably yield a compiler error as follows:
jeff@iscsi:
rm -f lib/libdast.a
make[1]: Entering directory `/home/
g++ -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c Socket.cpp
g++ -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c SocketAddr.cpp
g++ -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c Thread.cpp
g++ -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c delay.cpp
gcc -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c error.c
gcc -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c gnu_getopt.c
gcc -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c gnu_getopt_long.c
gcc -I../cfg -Wall -O2 -DHAVE_CONFIG_H -c signal.c
signal.c: In function ‘sig_exit’:
signal.c:170: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:
Preprocessed source stored into /tmp/ccYovWBk.out file, please attach this to your bugreport.
make[1]: *** [signal.o] Error 1
make[1]: Leaving directory `/home/
make: *** [lib/libdast.a] Error 2
--and--
jeff@iscsi:
make -C usr
make[1]: Entering directory `/home/
cc -O2 -fno-inline -Wall -Wstrict-prototypes -g -I../include -c -o ietd.o ietd.c
ietd.c: In function ‘usage’:
ietd.c:74: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:
Preprocessed source stored into /tmp/ccECYvLZ.out file, please attach this to your bugreport.
make[1]: *** [ietd.o] Error 1
make[1]: Leaving directory `/home/
make: *** [usr] Error 2
I just installed this system, and did an update/upgrade to pick up all the latest fixes - so I'm a little unsure if this is a generic problem with gcc-4.1 and amd64 (I hope not!) or something to do with kinks in the latest updates. Please help!
I have this problem on my amd64 gutsy as well. Is there a workaround?