On my ~x86 box, with make test libtool fails 2 of the 103 tests.... the following is full message Making check in tests make[1]: Entering directory `/var/tmp/portage/libtool-1.5.2-r6/work/libtool-1.5. 2/tests' make check-TESTS make[2]: Entering directory `/var/tmp/portage/libtool-1.5.2-r6/work/libtool-1.5. 2/tests' PASS: cdemo-static.test PASS: cdemo-make.test PASS: cdemo-exec.test PASS: demo-static.test PASS: demo-make.test PASS: demo-exec.test PASS: demo-inst.test PASS: demo-unst.test PASS: depdemo-static.test PASS: depdemo-make.test PASS: depdemo-exec.test PASS: depdemo-inst.test PASS: depdemo-unst.test PASS: mdemo-static.test PASS: mdemo-make.test PASS: mdemo-exec.test PASS: mdemo-inst.test PASS: mdemo-unst.test PASS: cdemo-conf.test PASS: cdemo-make.test PASS: cdemo-exec.test PASS: demo-conf.test PASS: demo-make.test PASS: demo-exec.test PASS: demo-inst.test PASS: demo-unst.test PASS: deplibs.test PASS: depdemo-conf.test PASS: depdemo-make.test PASS: depdemo-exec.test PASS: depdemo-inst.test PASS: depdemo-unst.test PASS: mdemo-conf.test PASS: mdemo-make.testPASS: mdemo-exec.test PASS: mdemo-inst.test PASS: mdemo-unst.test PASS: dryrun.test PASS: demo-nofast.test PASS: demo-make.test PASS: demo-exec.test PASS: demo-inst.test PASS: demo-unst.test PASS: demo-pic.test PASS: demo-make.test PASS: demo-exec.test PASS: demo-make.test PASS: demo-exec.test PASS: depdemo-nofast.test PASS: depdemo-make.test PASS: depdemo-exec.test PASS: depdemo-inst.test PASS: depdemo-unst.test PASS: cdemo-shared.test PASS: cdemo-make.test PASS: cdemo-exec.test PASS: demo-shared.test PASS: demo-make.test PASS: demo-exec.test PASS: demo-inst.test PASS: hardcode.test PASS: build-relink.test PASS: noinst-link.test PASS: demo-unst.test PASS: depdemo-shared.test PASS: depdemo-make.test PASS: depdemo-exec.test PASS: depdemo-inst.test PASS: build-relink2.test PASS: depdemo-unst.test PASS: mdemo-shared.test PASS: mdemo-make.test PASS: mdemo-exec.test PASS: mdemo-inst.test PASS: mdemo-unst.test FAIL: assign.test PASS: link.test PASS: link-2.test PASS: nomode.test PASS: quote.test FAIL: sh.test PASS: suffix.test PASS: pdemo-conf.test PASS: pdemo-make.test PASS: pdemo-exec.test PASS: pdemo-inst.test PASS: mdemo-conf.test PASS: mdemo-make.test PASS: mdemo2-conf.test PASS: mdemo2-make.test PASS: mdemo2-exec.test PASS: tagdemo-static.test PASS: tagdemo-make.test PASS: tagdemo-exec.test PASS: tagdemo-conf.test PASS: tagdemo-make.test PASS: tagdemo-exec.test PASS: tagdemo-shared.test PASS: tagdemo-make.test PASS: tagdemo-exec.test PASS: f77demo-static.test PASS: f77demo-make.test PASS: f77demo-exec.test PASS: f77demo-conf.test PASS: f77demo-make.test PASS: f77demo-exec.test PASS: f77demo-shared.test PASS: f77demo-make.test PASS: f77demo-exec.test ==================================== 2 of 109 tests failed Please report to bug-libtool@gnu.org ==================================== make[2]: *** [check-TESTS] Error 1 make[2]: Leaving directory `/var/tmp/portage/libtool-1.5.2-r6/work/libtool-1.5.2 /tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/var/tmp/portage/libtool-1.5.2-r6/work/libtool-1.5.2 /tests' make: *** [check-recursive] Error 1 !!! ERROR: sys-devel/libtool-1.5.2-r6 failed. !!! Function src_test, Line 520, Exitcode 0 !!! Make check failed. See above for details. !!! If you need support, post the topmost build error, NOT this status message. my emerge info is as follows dan@Linuxcomp ~ $ emerge info Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.4.2, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r3 i686) ================================================================= System uname: 2.6.9-gentoo-r3 i686 AMD Athlon(tm) XP 2500+ Gentoo Base System version 1.6.5 distcc[21161] (dcc_trace_version) distcc 2.18 i686-pc-linux-gnu; built Nov 5 20 04 19:00:00 [disabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /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 /us r/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks maketest sandbox sfperms" GENTOO_MIRRORS="http://mirrors.acm.cs.rpi.edu/gentoo/ http://gentoo.mirror.sdv.f r http://chod.cwru.edu/gentoo http://gentoo.mirrors.pair.com/" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X aim alsa apache2 apm arts avi berkdb bitmap-fonts cdb cdr crypt cups curl dvd db encode esd f77 flac foomatic foomaticdb ftp gdbm gif gpm gtk gtk2 imlib j ava jikes jpeg libg++ libwww mad mikmod motif mpeg msn mysql ncurses nls nptl np tlonly oggvorbis opengl oss pam pdflib perl php png posix ppds python quicktime readline samba sdl slang spell sqlite ssl svga tcpd tiff truetype usb x86 xml xm l2 xmms xv yahoo zlib" if you need any other info, let me know
ok, the assign.test failure is my fault, fixed that one in cvs ... the other failure's are probably because of our custom gentoo patches ... i'll look at fixing them up too
ok, the remaining bug is due to the files/1.4.3/libtool-1.4.2-portage.patch patch ... i'd rather not try to fix this because i'm afraid i'll break it bad ;) === Running sh.test 5204: eval mynewdependency_lib="`echo "$libdir/$name" |sed -e "s:$D::g" -e 's://:/:g'`" 5210: if test -z "`echo $newdependency_libs |grep -e "$mynewdependency_lib"`"; then 5223: if test -n "`echo $deplib |grep -e "$S"`" && test "$S"; then 5226: elif test -n "`echo $deplib |grep -e "$D"`" && test "$D"; then 5227: eval mynewdependency_lib="`echo "$deplib" |sed -e "s:$D::g" -e 's://:/:g'`" 5236: if test -z "`echo $newdependency_libs |grep -e "$mynewdependency_lib"`"; then 5294: install_libdir="`echo "$install_libdir" |sed -e "s:$D::g" -e 's://:/:g'`" nested quotes are dangerous
*** Bug 70646 has been marked as a duplicate of this bug. ***
hello. sorry for the bugspam but i'd just like some clarification. does this failure because of the patch mean that libtool will fail in certain situations in real world use, or just that the patch breaks something in the test but libtool is actually perfectly fine? i'm having a some strange stability errors i can't pin down so i'm rebuilding and need to be little paranoid about stuff like this right now. ;) thank you.
the patch is fine the test is just there for portability reasons ... if you're using bash-2 or bash-3 on a Gentoo Linux system, the test failure can be ignored on some older archaic systems, you would have to worry about it
*** Bug 72101 has been marked as a duplicate of this bug. ***
There's more information about this bug in bug #62698. Basically, this has been fixed upstream but only after libtool-1.9. I think this is still a problem and would prefer a patch rather than me having to remove maketest from my FEATURES.
i'm pretty sure the upstream fix you reference has nothing to do with this report the test failures we're experiencing are due to a patch *we* apply to fix some issue with portage building the way we do
*** Bug 73517 has been marked as a duplicate of this bug. ***
Created attachment 45686 [details, diff] libtool-1.5.2 sh.test failure patch Assuming everyone running gentoo is running bash as /bin/sh, this fixes the test. Given what the test is actually testing ("does code that was shipped as part of libtool pass this sanity check?"), I don't feel this patch is unreasonable. I'm still wondering how this was marked stable with this problem - I don't see a way that it could pass that test on any system.
This problem still occurs in 1.5.2-r7. It's been nearly 40 days since the last update. Any news?
40 days is still a brand new bug ;P fixed in cvs
