CVS mainline cp/spew.c failing to build
Gordon Sadler
gbsadler1@lcisp.com
Fri May 25 11:12:00 GMT 2001
stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -c -DIN_GCC -Os -march=i686 -fstrict-aliasing -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Icp -I/usr/src/cvs/gcc/gcc -I/usr/src/cvs/gcc/gcc/cp -I/usr/src/cvs/gcc/gcc/config -I/usr/src/cvs/gcc/gcc/../include /usr/src/cvs/gcc/gcc/cp/spew.c -o cp/spew.o
/usr/src/cvs/gcc/gcc/cp/spew.c: In function `snarf_method':
/usr/src/cvs/gcc/gcc/cp/spew.c:1178: Internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
make[2]: *** [cp/spew.o] Error 1
This is the followup I mentioned when reporting gcov failing.
On both/either of these failures, I have no idea if any kind of
pre-preocessed sources would be useful/appropriate. Both of these
failures have been happenning daily for quite some time. I did notice
that other arches, and even some ix86's have been producing useable
testresults. Now the question is why? is it Debian's gcc from unstable?
ld from unstable? possibly configure options? or maybe *C*FLAGS?
It looks like the auto build system uses fairly vanilla configure
options, but I don't think mine are extra-ordinary either.
Any ideas?
--
Gordon Sadler
More information about the Gcc
mailing list