I am trying to update gcc using emerge -U gcc. I have checked revdep and all is ok. I have tried this update 4 or 5 times over the last few days and it fails every time. Reproducible: Always Steps to Reproduce: 1.emerge -U gcc 2. 3. Actual Results: !!! ERROR: sys-devel/gcc-3.2.3-r1 failed. !!! Function src_compile, Line 354, Exitcode 2 !!! (no error message) var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/../include /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/predict.c -o predict.o gcc -c -DIN_GCC -O -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/config -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/../include /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/print-tree.c -o print-tree.o gcc -c -DIN_GCC -O -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/config -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/../include /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/profile.c -o profile.o /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/profile.c: In function `output_gcov_string': /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/profile.c:198: warning: signed and unsigned type in conditional expression gcc -c -DIN_GCC -O -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/config -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/../include /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/real.c -o real.o gcc -c -DIN_GCC -O -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/. -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/config -I/var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/../include /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/gcc/recog.c -o recog.o insn-recog.c: In function `split_2': insn-recog.c:53873: 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]: *** [insn-recog.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/var/tmp/portage/gcc-3.2.3-r1/work/build/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/var/tmp/portage/gcc-3.2.3-r1/work/build/gcc' make: *** [bootstrap-lean] Error 2 !!! ERROR: sys-devel/gcc-3.2.3-r1 failed. !!! Function src_compile, Line 354, Exitcode 2 !!! (no error message)
please post `emerge info`
Created attachment 14824 [details] emerge info emerge info...
Created attachment 14825 [details] gcc_mozilla.err this is the output of USE="-mozilla" emerge gcc 2> gcc.err use for ref to first bug...
Comment on attachment 14825 [details] gcc_mozilla.err reproductible error when emerge gcc 2> gcc_mozilla.err
hello, I have exactly the same error. This is reproductible ... included are two attachement with the error outputs for USE="-mozilla" emerge gcc 2> gcc.err (attachement gcc.err and gcc0.err) I also included my emerge info the following pb also arose if I tried to compile with mozilla flag it systematically crashes: here included is the error output for emerge gcc 2> gcc.err I have tried emerging from livecd with same result. I'm running kernel ppc-benh-2.4.21-r2. A bit of history... I have been trying to emerge gcc-3.2.3-r1 for a while now and it was seg faulting erratically. This seems to be an L2 cache pb, so I did: sysctl -w kernel.l2cr=0 And this has resolved erratic seg faulting when emerging large ebuilds... I hope that all this is relevant to this bug and will help in resolving it. If I should open a new bug please let me know... thank you and thanks again for the help...
Created attachment 14826 [details] gcc.err output for the following: USE="-mozilla" emerge gcc 2> gcc.err
Comment on attachment 14826 [details] gcc.err output of : USE="-mozilla" emerge gcc 2> gcc.err
Created attachment 14827 [details] gcc0.err
Comment on attachment 14827 [details] gcc0.err output of second try at: USE="-mozilla" emerge gcc 2> gcc2.err
Comment on attachment 14827 [details] gcc0.err output of 2nd attempt at: USE="-mozilla" emerge gcc 2> gcc2.err
Hi all, I have solved my problem, it was a memory issue. I removed the bad stick of ram, emerged gcc all all was well. This was such a random error that I have had over the last month with various emerges, some would work and others fail, a rerun usually caused it to fail at a different point. Thanks for all your efforts. regards Paul
bad memory issue
