Re: [gentoo-hardened] GCC upgrading from 3.4.6-r2 to 4.3.4 dies

[Gordon Malm]

On Monday, February 1, 2010 06:46:32 Kārlis Repsons wrote:
> People,
> perhaps someone has an idea of why that happens (or what should I check):
>
> # emerge gcc
> throws out: "i686-pc-linux-gnu-gcc: Internal error: Killed (program cc1)"
> (for a wider sample see the bottom of this mail)
>
> 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: # USE="-hardened" emerge --oneshot
> =sys-libs/glibc-2.5
> # USE="-hardened" emerge --oneshot =sys-devel/gcc-4.1.2
> 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?
>
> If you know, please let me know too...
>
>
> [0]
> http://archives.gentoo.org/gentoo-hardened/msg_bc73e13380fcad0c682047dd5cb0
>29e3.xml [1] http://www.gentoo.org/doc/en/gcc-upgrading.xml#doc_chap2
> [2] http://www.gentoo.org/proj/en/hardened/toolchain-upgrade-guide.xml
>
>
> ======================================================
> 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. -
> 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 -
> 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-
> devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libdecnumber/bid -I../libdecnumber
> insn-attrtab.c -o insn-attrtab.o i686-pc-linux-gnu-gcc: Internal error:
> Killed (program cc1)
> Please submit a full bug report.
> See <URL:http://bugs.gentoo.org/> for instructions.
> make[3]: *** [insn-attrtab.o] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build/gcc' make[2]: ***
> [all-stage1-gcc] Error 2
> make[2]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build' make[1]: ***
> [stage1-bubble] Error 2
> make[1]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build' make: ***
> [bootstrap-lean] Error 2
>  * ERROR: sys-devel/gcc-4.3.4 failed:
>  *   emake failed with bootstrap-lean
>  *
>  * Call stack:
>  *     ebuild.sh, line   54:  Called src_compile
>  *   environment, line 4988:  Called toolchain_src_compile
>  *   environment, line 5550:  Called gcc_src_compile
>  *   environment, line 3173:  Called gcc_do_make
>  *   environment, line 2963:  Called die
>  * The specific snippet of code:
>  *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
> LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die
> "emake failed with ${GCC_MAKE_TARGET}";
> ======================================================

emerge --info please.


Gordon Malm (gengor)