Summary: | glibc-2.3.4.20050125 failes to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | barthek <gejzer> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | tetromino |
Priority: | High | ||
Version: | 2004.3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
barthek
2005-02-21 07:04:21 UTC
Very similar error here. I was using USE="-build -debug +erandom +hardened (-multilib) +nls -nomalloccheck +nptl -nptlonly +pic +userlocales" gcc-config is i686-pc-linux-gnu-3.4.3 (hardened) i686-pc-linux-gnu-gcc /var/tmp/portage/glibc-2.3.4.20050125/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crtn.S -c -I../include -I. -I/var/tmp/portage/glibc-2.3.4.20050125/work/build-default-i686-pc-linux-gnu-linuxthreads/csu -I.. -I../libio -I/var/tmp/portage/glibc-2.3.4.20050125/work/build-default-i686-pc-linux-gnu-linuxthreads -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/include -isystem /usr/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -DHAVE_INITFINI -DASSEMBLER -I/var/tmp/portage/glibc-2.3.4.20050125/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/. -DGAS_SYNTAX -g0 -o /var/tmp/portage/glibc-2.3.4.20050125/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crtn.o i686-pc-linux-gnu-gcc: Internal error: Segmentation fault (program as) Please submit a full bug report. See <URL:http://bugs.gentoo.org/> for instructions. make[2]: *** [/var/tmp/portage/glibc-2.3.4.20050125/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crti.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20050125/work/glibc-2.3.4/csu' make[1]: *** [csu/subdir_lib] Error 2 make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20050125/work/glibc-2.3.4' make: *** [all] Error 2 !!! ERROR: sys-libs/glibc-2.3.4.20050125 failed. !!! Function toolchain-glibc_src_compile, Line 187, Exitcode 2 Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r4 i686) ================================================================= System uname: 2.6.10-gentoo-r4 i686 Intel(R) Pentium(R) 4 CPU 1.60GHz Gentoo Base System version 1.6.9 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 23 2005, 02:20:56)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r3 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -pipe -frename-registers -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" Addition note: error only occurs on pentium 4 system. On my athlon xp box, everything builds fine. My problems were caused by broken binutils. After I emerged a known-good binutils package, glibc-2.3.4.20050125 emerged fine. hmm the 'as' i am using never failed me, but i am still getting those LC2 and LC3 undefined symbols... :\ i re-emerged binutils and gcc, but glibc still fails to build. what am i supposed to do now ? |