| Summary: | glibc 2.3.4.20041102-r1 fails to build in globtest.sh | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Lawson <daniel> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | deathwing00 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I think this is a duplicate of bug #81258 I got the same problem when trying to upgrade from 2004.3 to 2005.0 on an AMD64, but I did got around to it (after trying a lot of things mind you). I've been doing the upgrade loged-in as my user and using 'su' to gain root privilages. However, when I directly loged-in as root, glibc complied and installed cleanly. You might want to try this. Ioannis: This does look similar to bug 81258, however it's a different version of glibc. Not sure how that affects your bug tracking process. Further update: if I remove the "test" FEATURE, it builds fine. So this isn't a show stopper or anything, however there's little point having a test suite if it's not used (and when it does get used, it fails). I'm willing to try suggestions. |
glibc fails to complete the build process due to a failure in globtest.sh. I see there have been at least one other bug (bug id 85782) submitted regarding this, but it was duped incorrectly. All bugs relating to glibc build failures seem to suggest that an emerge sync, as of 25 Mar 2005, followed by re-emerging glibc will fix this issue. This does not seem to be the case. I have done the following: rm -f /usr/portage/distfiles/* rm -f /usr/portage/sys-libs/glibc/* emerge sync cat /usr/portage/sys-libs/glibc/glibc-2.3.4.20041102-r1.ebuild | grep Header # $Header: /var/cvsroot/gentoo-x86/sys-libs/glibc/glibc-2.3.4.20041102-r1.ebuild,v 1.5 2005/03/25 06:17:28 vapier Exp $ emerge glibc glibc fails to build with the following error: /bin/sh -e globtest.sh /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/ /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/elf/ \ ld-linux.so.2 make[2]: *** [/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/posix/globtest.out] Error 1 make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3/posix' make[1]: *** [posix/tests] Error 2 make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3' make: *** [check] Error 2 Running this test manually results in: ./globtest.sh /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/ /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/elf/ ld-linux.so.2; echo $? 0 Ie, it is exiting with a runlevel of 0, so the test is succeeding if I run it manually. It was suggested that disabling parallel builds might fix this bug. I tried setting MAKEOPTS=-j1 and emerging glibc; this also didn't work. I can't offer any suggestions on how to fix it, other than the Makefile appears to assume the globtest.out file is created in $(objpfx), when globtest.sh creates it under /tmp and deletes it once it is finished. Reproducible: Always Steps to Reproduce: 1. emerge glibc 2. 3. Actual Results: /bin/sh -e globtest.sh /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/ /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/elf/ \ ld-linux.so.2 make[2]: *** [/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/posix/globtest.out] Error 1 make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3/posix' make[1]: *** [posix/tests] Error 2 make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3' make: *** [check] Error 2 Expected Results: glibc should build emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.11-gentoo-r4 i686) ================================================================= System uname: 2.6.11-gentoo-r4 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 10 2005, 15:33:53)] ccache version 2.3 [enabled] 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 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms test" GENTOO_MIRRORS="http://gentoo.osuosl.org" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="apache2 apm arts avi bash-completion berkdb bitmap-fonts crypt curl dnsdb drac emboss encode exiscan-acl foomaticdb fortran gd gdbm gif gmp gpm idled imagemagick imap imlib ipv6 jpeg ldap libg++ libwww lmtp mad maildir mcal mikmod motif mp3 mpeg msn mysql ncurses nls oggvorbis opengl oscar oss pam pdflib perl pic png postgres python quicktime readline sasl sdl slang snmp spell spf srs ssl svga tcpd tetex tiff truetype truetype-fonts type1-fonts vhosts wildlsearch wildsearch x86 xml2 xmms yahoo zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS