1 |
People, |
2 |
perhaps someone has an idea of why that happens (or what should I check): |
3 |
|
4 |
# emerge gcc |
5 |
throws out: "i686-pc-linux-gnu-gcc: Internal error: Killed (program cc1)" (for a wider sample see the bottom of this mail) |
6 |
|
7 |
Looking through archives of this list [0], I understood, that, as per [1] I should start with a gcc upgrade... Also I wonder, if I did as per [2] and proceed with vanilla gcc as: |
8 |
# USE="-hardened" emerge --oneshot =sys-libs/glibc-2.5 |
9 |
# USE="-hardened" emerge --oneshot =sys-devel/gcc-4.1.2 |
10 |
isn't there a risk, that I've compiled a whole system for hardened glibc and recompiling and replacing it just crashes the whole thing? |
11 |
|
12 |
If you know, please let me know too... |
13 |
|
14 |
|
15 |
[0] http://archives.gentoo.org/gentoo-hardened/msg_bc73e13380fcad0c682047dd5cb029e3.xml |
16 |
[1] http://www.gentoo.org/doc/en/gcc-upgrading.xml#doc_chap2 |
17 |
[2] http://www.gentoo.org/proj/en/hardened/toolchain-upgrade-guide.xml |
18 |
|
19 |
|
20 |
====================================================== |
21 |
i686-pc-linux-gnu-gcc -c -O -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -I. -I. - |
22 |
I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../include - |
23 |
I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libcpp/include -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libdecnumber -I/var/tmp/portage/sys- |
24 |
devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libdecnumber/bid -I../libdecnumber insn-attrtab.c -o insn-attrtab.o |
25 |
i686-pc-linux-gnu-gcc: Internal error: Killed (program cc1) |
26 |
Please submit a full bug report. |
27 |
See <URL:http://bugs.gentoo.org/> for instructions. |
28 |
make[3]: *** [insn-attrtab.o] Error 1 |
29 |
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build/gcc' |
30 |
make[2]: *** [all-stage1-gcc] Error 2 |
31 |
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build' |
32 |
make[1]: *** [stage1-bubble] Error 2 |
33 |
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build' |
34 |
make: *** [bootstrap-lean] Error 2 |
35 |
* ERROR: sys-devel/gcc-4.3.4 failed: |
36 |
* emake failed with bootstrap-lean |
37 |
* |
38 |
* Call stack: |
39 |
* ebuild.sh, line 54: Called src_compile |
40 |
* environment, line 4988: Called toolchain_src_compile |
41 |
* environment, line 5550: Called gcc_src_compile |
42 |
* environment, line 3173: Called gcc_do_make |
43 |
* environment, line 2963: Called die |
44 |
* The specific snippet of code: |
45 |
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with |
46 |
${GCC_MAKE_TARGET}"; |
47 |
====================================================== |