When I try to update from glibc-2.3.4.20050125 to glibc-2.3.4.20050125-r1 I get the following error: loadmsgcat.c: In function `_nl_init_domain_conv': ../sysdeps/i386/bits/string.h:655: error: can't find a register in class `GENERAL_REGS' while reloading `asm' make[2]: *** [/var/tmp/portage/glibc-2.3.4.20050125-r1/work/build-default-i386-pc-linux-gnu-linuxthreads/intl/loadmsgcat.os] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20050125-r1/work/glibc-2.3.4/intl' make[1]: *** [intl/subdir_lib] Error 2 make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20050125-r1/work/glibc-2.3.4' make: *** [all] Error 2 !!! ERROR: sys-libs/glibc-2.3.4.20050125-r1 failed. !!! Function toolchain-glibc_src_compile, Line 237, Exitcode 2 Reproducible: Always Steps to Reproduce: 1.add "sys-libs/glibc ~x86" to /etc/portage/package.keywords 2.emerge -u --deep world 3. Actual Results: I get the error posted above. Expected Results: Compiled and installed successfully. bash-2.05b# emerge --info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.11-gentoo-r4 i686) ================================================================= System uname: 2.6.11-gentoo-r4 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 10 2005, 23:07:00)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mtune=athlon -march=athlon -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=athlon -march=athlon -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dvd emboss encode fam foomaticdb fortran gdbm gif gpm imlib ipv6 jpeg kde libg++libwww mad mikmod motif mp3 mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl spell ssl svg svga tcpd tiff truetype truetype-fonts type1-fonts x86 xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Same problem here. I don't need to put the sys-libs/glib in the package.keywords to reproduce. I tried some sujections like adding the -mmx to the use flags but that did not work
I tried compiling this same version on my other gentoo system also getting the same error.
Bug #82424 might be the cause of this.
One thing everybody with this problem has in common is that they are all using CHOST="i386-pc-linux-gnu" and linuxthreads. I'm going to try to reproduce it in a chroot. Btw, this is a common problem: http://forums.gentoo.org/viewtopic-t-327199.html http://forums.gentoo.org/viewtopic-t-326464.html http://forums.gentoo.org/viewtopic-t-319595.html http://forums.gentoo.org/viewtopic-t-324167.html http://forums.gentoo.org/viewtopic-t-314053.html http://forums.gentoo.org/viewtopic-t-309625.html
I removed -fomit-frame-pointer from my CFLAGS and reran emerge -u glibc and it compiled successfully on both my systems. Hooray! Do I close the bug or do the toolchain maintainers?
Don't close it! This is still a problem for everbody on i386-pc-linux-gnu with -fomit-frame-pointer in their CFLAGS. I was able to reproduce this bug in a chroot and it only seems to affect i386-pc-linux-gnu users so the ebuild should be modified to only --enable-omitfp if the CHOST is i686-pc-linux-gnu or any other non x86 arch (I don't know about 1485 and i586).
This is fixed in a commit I made yesterday or the day before.