1 |
Today I attempted a bootstrapping from scratch, on an x86 Linux host, and applying |
2 |
the fix suggested in <http://bugs.gentoo.org/show_bug.cgi?id=215304>. |
3 |
|
4 |
I was fairly convinced that everything should go well, having done a very similar |
5 |
bootstrapping in the early morning of 2008-03-30. |
6 |
|
7 |
The problem occurred when emerging gcc, as part of the first `emerge -e system'. Here |
8 |
are some lines from the console log: |
9 |
|
10 |
---------- |
11 |
|
12 |
if [ x"-fpic" != x ]; then \ |
13 |
/local/scratch/portage/sys-devel/gcc-4.3.0/work/build/./prev-gcc/xgcc |
14 |
-B/local/scratch/portage/sys-devel/gcc-4.3.0/work/build/./prev-gcc/ |
15 |
-B/local/scratch/nightly/2008-03-31/usr/i686-pc-linux-gnu/bin/ -c -DHAVE_CONFIG_H |
16 |
-fprofile-use -I. |
17 |
-I/local/scratch/portage/sys-devel/gcc-4.3.0/work/gcc-4.3.0/libiberty/../include -W |
18 |
-Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic -fpic |
19 |
/local/scratch/portage/sys-devel/gcc-4.3.0/work/gcc-4.3.0/libiberty/hashtab.c -o |
20 |
pic/hashtab.o; \ |
21 |
else true; fi |
22 |
/local/scratch/portage/sys-devel/gcc-4.3.0/work/gcc-4.3.0/libiberty/hashtab.c: In |
23 |
function 'htab_expand': |
24 |
/local/scratch/portage/sys-devel/gcc-4.3.0/work/gcc-4.3.0/libiberty/hashtab.c:554: |
25 |
internal compiler error: Segmentation fault |
26 |
Please submit a full bug report, |
27 |
with preprocessed source if appropriate. |
28 |
See <http://bugs.gentoo.org/> for instructions. |
29 |
make[3]: *** [hashtab.o] Error 1 |
30 |
make[3]: Leaving directory |
31 |
`/local/scratch/portage/sys-devel/gcc-4.3.0/work/build/libiberty' |
32 |
make[2]: *** [all-stagefeedback-libiberty] Error 2 |
33 |
make[2]: Leaving directory `/local/scratch/portage/sys-devel/gcc-4.3.0/work/build' |
34 |
make[1]: *** [stagefeedback-bubble] Error 2 |
35 |
make[1]: Leaving directory `/local/scratch/portage/sys-devel/gcc-4.3.0/work/build' |
36 |
make: *** [profiledbootstrap] Error 2 |
37 |
* ERROR: sys-devel/gcc-4.3.0 failed: |
38 |
* emake failed with profiledbootstrap |
39 |
* |
40 |
* Call stack: |
41 |
* ebuild.sh: 49: <call src_compile> |
42 |
* environment:4690: <call gcc_src_compile> |
43 |
* environment:2950: <call gcc_do_make> |
44 |
* environment:2780: emake LDFLAGS="${LDFLAGS}" |
45 |
STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" |
46 |
${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}"; |
47 |
* |
48 |
* If you need support, post the topmost build error, and the call stack if relevant. |
49 |
* build log: '/local/scratch/portage/sys-devel/gcc-4.3.0/temp/build.log' |
50 |
* ebuild environment: '/local/scratch/portage/sys-devel/gcc-4.3.0/temp/environment' |
51 |
* S: '/local/scratch/portage/sys-devel/gcc-4.3.0/work/build' |
52 |
|
53 |
------------- |
54 |
|
55 |
The problem is reproducible for me. When it happened the first time I suspected that |
56 |
my MAKEOPTS=-j2 might cause the problem (it is a dual core host), so I removed it and |
57 |
re-ran, with precisely the same result. |
58 |
|
59 |
My successful bootstrapping some day ago took a different path as regards gcc: |
60 |
`emerge -e system' got me gcc-4.2.3, and a subsequent `emerge --sync && emerge -vuND |
61 |
world' (several hours after bootstrapping) got me gcc-4.3.0. |
62 |
|
63 |
The host gcc is 4.1.2/SUSE. Perhaps the climb from 4.1.2 to 4.3.0 is just too steep, |
64 |
but doable if using 4.2.3 as a stepping stone? |
65 |
|
66 |
--Rabbe |
67 |
-- |
68 |
gentoo-alt@l.g.o mailing list |