Segmentation fault when trying to emerge gcc-4.3.0
Today I attempted a bootstrapping from scratch, on an x86 Linux host, and applying
the fix suggested in <http://bugs.gentoo.org/show_bug.cgi?id=215304>.
I was fairly convinced that everything should go well, having done a very similar
bootstrapping in the early morning of 2008-03-30.
The problem occurred when emerging gcc, as part of the first `emerge -e system'. Here
are some lines from the console log:
if [ x"-fpic" != x ]; then
-B/local/scratch/nightly/2008-03-31/usr/i686-pc-linux-gnu/bin/ -c -DHAVE_CONFIG_H
-Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic -fpic
else true; fi
internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.
make: *** [hashtab.o] Error 1
make: Leaving directory
* If you need support, post the topmost build error, and the call stack if relevant.
* build log: '/local/scratch/portage/sys-devel/gcc-4.3.0/temp/build.log'
* ebuild environment: '/local/scratch/portage/sys-devel/gcc-4.3.0/temp/environment'
* S: '/local/scratch/portage/sys-devel/gcc-4.3.0/work/build'
The problem is reproducible for me. When it happened the first time I suspected that
my MAKEOPTS=-j2 might cause the problem (it is a dual core host), so I removed it and
re-ran, with precisely the same result.
My successful bootstrapping some day ago took a different path as regards gcc:
`emerge -e system' got me gcc-4.2.3, and a subsequent `emerge --sync && emerge -vuND
world' (several hours after bootstrapping) got me gcc-4.3.0.
The host gcc is 4.1.2/SUSE. Perhaps the climb from 4.1.2 to 4.3.0 is just too steep,
but doable if using 4.2.3 as a stepping stone?
email@example.com mailing list