I'm running Gentoo-PPC on an iBook G4. I tried to update to glibc-2.3.4.20050125-r1, but it failed with the error message: FAILED: postinstall (and then some number, sorry, I didn't write it down) After that, nothing worked any more: anything just exited with a segmentation fault. Now Gentoo refuses to boot, it just freezes at some point, and I can't even chroot into the system via LiveCD (bash segfaults). From the LiveCD, tail /mnt/gentoo/var/log/emerge.log reports: >>> emerge sys-libs/glibc-2.3.4.20050125-r1 to / === Cleaning (sys-libs/glibc-2.3.4.20050125-r1::usr/portage/sys-libs/glibc/glibc-2.3.4.20050125-r1.ebuild) === Compiling/Merging (sys-libs/glibc-2.3.4.20050125-r1::usr/portage/sys-libs/glibc/glibc-2.3.4.20050125-r1.ebuild) *** terminating Portage obviously compiled & installed the new glibc, but then failed for some reason before doing the post-installation stuff. Reproducible: Didn't try Steps to Reproduce: 1.emerge glibc 2. 3. Actual Results: Installation ended prematurely, rendering the whole machine unusable. Expected Results: Updated glibc. Portage 2.0.51.19 (default-linux/ppc/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20041102-r1, 2.6.10-gentoo-r6 ppc) ================================================================= System uname: 2.6.10-gentoo-r6 ppc 7447A, altivec supported Gentoo Base System version 1.6.10 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Mar 24 2005, 22:48:53)] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.9.5, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.90.0.3-r4 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="ppc ~ppc" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=7400 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe -mpowerpc-gfxopt" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/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 -mcpu=7400 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe -mpowerpc-gfxopt" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/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 -mcpu=7400 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe -mpowerpc-gfxopt" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X a52 aac alsa altivec berkdb bitmap-fonts cdr crypt cups curl divx4linux dv dvd emboss fam fbcon ffmpeg flac font-server fortran gdbm gif gtk gtk2 imagemagick imap imlib jpeg kde lcms mad matroska mikmod mp3 mpeg ncurses nls nodrm nptl oggvorbis opengl pam perl png ppc python qt quicktime radeon readline sdl slang sndfile ssl tcltk theora tiff truetype truetype-fonts type1-fonts unicode xml xml2 xprint xv zlib linguas_en linguas_fi" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY (Sorry, this is a bit outdated file, for example LANG & LC_ALL are now fi_FI, but it's all I've got. This was saved on another computer)
I can confirm this bug. These are the last two lines of the emerge: >>> Safely unmerging already-installed instance... !!! FAILED perm: 2816 emerge info is at http://dev.gentoo.org/~hansmi/misc/emerge-info-g5
FWIW, I got this same error, but I thought it was some problem on my side, as I had get out of memory because of another process and had to restart the ebuild. I booted using LiveCD, chrooted into the machine, and, after some tests, when I re-emerged with +nptlonly, it worked like a charm. So I think it is related with linuxthread fallback, but I could be wrong, as I had a couple downgrades and upgrades of the binary thinking that something was wrong.
Please do 'ls /lib/libpthread*' on the troubled system. If you update the system using +nptl -nptlonly, remove /lib/libpthread-2.3.4.so if it exists there, and then run ldconfig.
Created attachment 55582 [details] glibc-2.3.4.20050125-r1.ebuild Please try this updated ebuild
Created attachment 55608 [details] glibc-2.3.4.20050125-r1.ebuild Actually, that last one won't work, but this one will...
ppc: Please test/rekeyword
Tested on my stable chroot, with USE="nptl -nptlonly". Failed with: !!! FAILED postinst: 2816. ls -la /lib/libpthread* returns: -rwxr-xr-x 1 root root 108183 Apr 11 05:15 /lib/libpthread-0.10.so lrwxrwxrwx 1 root root 18 Apr 11 05:16 /lib/libpthread.so.0 -> libpthread-0.10.so In the output from the build, the only other strange things were repeated shell-init errors durin the install phase/during binary stripping: shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory This chroot has always been built with USE="nptl -nptlonly" and I didn't change the flags. Let me know if there's anything else I can test for you.
I was able to emerge this version of Glibc without any problems on my G4 based Pegasos machine. And I use it right now without any problems (+nptl +nptlonly)
The problem only seems to occur with +nptl -nptlonly, but thanks for testing.
This no longer fails during the emerge, can we close this bug?
Closing the bug as it fails in a different way now (same as 2.3.5): http://bugs.gentoo.org/show_bug.cgi?id=92794
*** Bug 80113 has been marked as a duplicate of this bug. ***
