When running ~x86, the glibc snapshots (all of them apparently; I've hit numerous) don't work. By some black magic, enabling USE="nptl" causes gcc to segfault while compiling glibc. This is possibly a gcc problem, and I've only tested on numerous revisions of 3.3.2. Nothing else eseems to have a problem, however. I suggest you hard-mask the glibc snapshots from the 2.3.3 glibc branch, as they're causing a large annoyance to me running ~x86. Can anyone else confirm that 2.3.3_pre* doesn't like to compile, particularly with other versions of gcc? It would be better to get more data on the matter before hard-masking glibc.
I compiled multiple glibc-2.3.3_pres with gcc-3.3.2 and USE="nptl" no problem.
2.3.3_pre20040207 with USE="nptl" compiles/works fine here as well.
Hmm, sorry I should have included my emerge info. I also have pic on as well. Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3-rc2) ================================================================= System uname: 2.6.3-rc2 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.13 distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r2 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache distcc fixpackages sandbox userpriv usersandbox" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://www.gtlib.cc.gatech.edu/pub/gentoo http://mirrors.tds.net/gentoo" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="3dnow 3ds X aalib alsa apm arts avi berkdb cdr crypt cups dga directfb dvd encode esd fbcon foomaticdb gdbm gif gimpprint gnome gpm gstreamer gtk gtk2 gtkhtml guile imlib java jbig jpeg justify kerberos krb4 lcms ldap libg++ libwww mad mikmod mmx mng motif mozilla mpeg ncurses nls nptl offensive oggvorbis openal opengl oss pam pdflib perl pic pie png ppds python qt quicktime readline samba sdl slang speex spell sse ssl svga tcltk tcpd tiff truetype wmf x86 xml xml2 xmms xv zlib"
Works fine here. Any chance you can add a log of the failing, and include output of 'gcc --version' ? Also, do you use grsecurity/selinux/hardened-gcc?
I use hardened-gcc. I'll copy/paste the failure but you know it'll be about an hour before I can get to it; it's FAR in. Right now I'm on 2.6.3-rc2 with PaX, OpenPax, and Linux Jail patches applied; however I've hit this on a 2.6.3-pax-openpax kernel as well, and I don't believe it's due to pax or openpax.
../sysdeps/generic/libc-start.c: In function `__libc_start_main': ../sysdeps/generic/libc-start.c:188: warning: implicit declaration of function `__guard_setup' gcc ../sysdeps/i386/i686/hp-timing.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -freorder-blocks -march=athlon-xp -pipe -mpreferred-stack-boundary=4 -I../include -I. -I/var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2/buildhere/csu -I.. -I../libio -I../nptl -I/var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2/buildhere -I../sysdeps/i386/elf -I../nptl/sysdeps/unix/sysv/linux/i386/i686 -I../nptl/sysdeps/unix/sysv/linux/i386 -I../nptl/sysdeps/unix/sysv/linux -I../nptl/sysdeps/pthread -I../sysdeps/pthread -I../nptl/sysdeps/unix/sysv -I../nptl/sysdeps/unix -I../nptl/sysdeps/i386/i686 -I../nptl/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../nptl/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-lib/i686-pc-linux-gnu/3.3.2/include -isystem /lib/modules/2.6.3-rc2/build/include -D_LIBC_REENTRANT -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DHAVE_INITFINI -o /var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2/buildhere/csu/hp-timing.o -MD -MP -MF /var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2/buildhere/csu/hp-timing.o.dt ../sysdeps/generic/libc-tls.c: In function `__libc_setup_tls': ../sysdeps/generic/libc-tls.c:199: error: can't find a register in class `BREG' while reloading `asm' distcc[13585] ERROR: compile on 192.168.0.3 failed make[2]: *** [/var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2/buildhere/csu/libc-tls.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/data/sysdirs/var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2/csu' make[1]: *** [csu/subdir_lib] Error 2 make[1]: Leaving directory `/data/sysdirs/var/tmp/portage/glibc-2.3.3_pre20040207/work/glibc-2.3.2' make: *** [all] Error 2 !!! ERROR: sys-libs/glibc-2.3.3_pre20040207 failed. !!! Function src_compile, Line 523, Exitcode 2 !!! (no error message) That's with HCC off, dunno about the breg error. That's odd. Maybe from +pic?
I've gotten a similar error when using distcc, but compiling localy was successful. I'm just running straight gentoo, no selinux, hardened-gcc or anything.
Ahh forgot about distcc. I just got that working yesterday. I'm now compiling with distcc off (FEATURES="-distcc" emerge...). If it works, I'll tell you. If it breaks, be prepared for another chunk of messages. Sorry for the unuseful data earlier. ^-^ This will take about an hour and a half if it's the one I've been getting from before, so don't just vulture over this bug for the next hour, those of you that are staring at it trying to figure out what the heck's going on.
it seems to work now. Odd. I was sure I did that numerous times with prior snapshots before i started using distcc, and with hcc off. Sorry. just close it.
