Re: testsuite: 24 25 64 failed

[Nix]

On 24 Mar 2008, Ralf Wildenhues verbalised:

> Hello Nix,
>
> Thanks for the testsuite feedback.

Most of it reduces to `my bizarre configuration broke your finely-honed
testsuite' and doesn't actually indicate a fault in libtool per se, so
I'm not sure quite how useful it actually is :)

> * Nix wrote on Fri, Mar 21, 2008 at 08:01:13PM CET:
>> 
>> The underlying cause of test 24's failure appears to be that LDFLAGS is
>> not consistently propagated down: note that a lot of the link steps do
>> not pass in my LDFLAGS of -specs=specs.no-as-needed, so get linked with
>> --as-needed (which is the default on my system) and subsequently
>> fail. (FWIW the only things I've ever seen fail with --as-needed are
>> linker-semantics testsuites like this one. :)
>
> First, you can try
>   LDFLAGS=-Wc,-specs=specs.no-as-needed

It seems to me that adding -Wl to the LDFLAGS wouldn't do anything
useful: it's the compiler driver that interprets the specs file, not the
linker. (And -Wc doesn't exist :) )

Hm, yes, it's not useful:

configure:3038: checking for C compiler default output file name
configure:3065: gcc   -Wc,-specs=specs.no-as-needed conftest.c  >&5
cc1: error: unrecognized command line option "-Wc,-specs=specs.no-as-needed"

configure:3038: checking for C compiler default output file name
configure:3065: gcc   -Wl,-specs=specs.no-as-needed conftest.c  >&5
/usr/bin/ld: unrecognized option '-specs=specs.no-as-needed'
/usr/bin/ld: use the --help option for usage information
collect2: ld returned 1 exit status

>                                             Second, we've had a test
> report that consistently used -Wl,--as-needed which only failed the
> template subdir test (and that failure is due to a bug in the test).

Ah, right, that's what I figured, but I wanted to be paranoid before I
built stuff with this which got rolled out to my vast audience of a few
thousand long-suffering in-house sods. :)

>> Test 25's failure is weirder and I don't know what its cause might be yet.
>
> It looks weird because you have configured 
>   --enable-shared --disable-static
>
> but somehow it seems the test fails to properly detect that.
> Please post the output of
>   make check-local TESTSUITEFLAGS='-v -d -x -k "static linking"'

Here:

abs_srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd . && pwd`; cd tests; \
        CONFIG_SHELL="/bin/sh" /bin/sh $abs_srcdir/tests/testsuite \
          MAKE="make" CC="gcc" CFLAGS="-g -O2" CPP="gcc -E" CPPFLAGS="" 
LD="/usr/bin/ld" LDFLAGS="" LIBS="-ldl " LN_S="ln -s" NM="/usr/bin/nm -B" 
RANLIB="ranlib" STRIP="strip" OBJEXT="o" EXEEXT="" SHELL="/bin/sh" 
CONFIG_SHELL="/bin/sh" CXX="g++" CXXFLAGS="-g -O2" CXXCPP="g++ -E" F77="g77" 
FFLAGS="-g -O2" FC="gfortran" FCFLAGS="-g -O2" GCJ="gcj" GCJFLAGS="-g -O2" 
_lt_pkgdatadir="/usr/packages/libtool/i686-hades" 
LIBTOOLIZE="/usr/packages/libtool/i686-hades/libtoolize" 
LIBTOOL="/usr/packages/libtool/i686-hades/libtool" 
tst_aclocaldir="/usr/packages/libtool/i686-hades/libltdl/m4" -v -d -x -k 
"static linking"
## ----------------------- ##
## libtool 2.2 test suite. ##
## ----------------------- ##
25. static.at:68: testing ...
+ LDFLAGS=' -no-undefined'
++ pwd
+ prefix=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst
+ bindir=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst/bin
++ pwd
+ prefix1=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1
++ pwd
+ prefix2=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2
++ pwd
+ prefix3=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3
+ libdir1=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib
+ libdir2=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib
+ libdir3=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
++ pwd
+ 
srcdir_broken=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken-src
++ pwd
+ prefix_broken=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken
+ 
libdir_broken=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
+ 
bindir_broken=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/bin
+ have_static=false
+ have_shared=false
+ per_deplib=false
+ /usr/packages/libtool/i686-hades/libtool --features
+ grep 'enable static libraries'
+ /usr/packages/libtool/i686-hades/libtool --features
+ grep 'enable shared libraries'
+ have_shared=:
++ /usr/packages/libtool/i686-hades/libtool --config
++ /usr/bin/grep -E 
'^(per_deplib_(static|dynamic)_flag|shlibpath_var|link_static_flag)='
+ eval shlibpath_var=LD_LIBRARY_PATH 'link_static_flag="-static"'
++ shlibpath_var=LD_LIBRARY_PATH
++ link_static_flag=-static
+ test -n ''
+ mkdir /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken-src 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
+ cd /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken-src
+ echo 'int this_should_not_be_linked_against() { return 0; }'
+ /usr/packages/libtool/i686-hades/libtool --mode=compile gcc -g -O2 -c a.c
libtool: compile:  gcc -g -O2 -c a.c  -fPIC -DPIC -o .libs/a.o
+ for i in 1 1dep 2 2dep 3 3dep
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba1.la a.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
libtool: link: gcc -shared  .libs/a.o      -Wl,-soname -Wl,liba1.so.0 -o 
.libs/liba1.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba1.so.0" && ln -s "liba1.so.0.0.0" 
"liba1.so.0")
libtool: link: (cd ".libs" && rm -f "liba1.so" && ln -s "liba1.so.0.0.0" 
"liba1.so")
libtool: link: ( cd ".libs" && rm -f "liba1.la" && ln -s "../liba1.la" 
"liba1.la" )
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp liba1.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba1.la
libtool: install: cp .libs/liba1.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba1.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba1.so.0.0.0 liba1.so.0 || { rm -f liba1.so.0 && ln -s liba1.so.0.0.0 
liba1.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba1.so.0.0.0 liba1.so || { rm -f liba1.so && ln -s liba1.so.0.0.0 
liba1.so; }; })
libtool: install: cp .libs/liba1.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba1.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ for i in 1 1dep 2 2dep 3 3dep
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba1dep.la a.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
libtool: link: gcc -shared  .libs/a.o      -Wl,-soname -Wl,liba1dep.so.0 -o 
.libs/liba1dep.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba1dep.so.0" && ln -s 
"liba1dep.so.0.0.0" "liba1dep.so.0")
libtool: link: (cd ".libs" && rm -f "liba1dep.so" && ln -s "liba1dep.so.0.0.0" 
"liba1dep.so")
libtool: link: ( cd ".libs" && rm -f "liba1dep.la" && ln -s "../liba1dep.la" 
"liba1dep.la" )
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp liba1dep.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba1dep.la
libtool: install: cp .libs/liba1dep.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba1dep.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba1dep.so.0.0.0 liba1dep.so.0 || { rm -f liba1dep.so.0 && ln -s 
liba1dep.so.0.0.0 liba1dep.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba1dep.so.0.0.0 liba1dep.so || { rm -f liba1dep.so && ln -s 
liba1dep.so.0.0.0 liba1dep.so; }; })
libtool: install: cp .libs/liba1dep.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba1dep.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ for i in 1 1dep 2 2dep 3 3dep
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba2.la a.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
libtool: link: gcc -shared  .libs/a.o      -Wl,-soname -Wl,liba2.so.0 -o 
.libs/liba2.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba2.so.0" && ln -s "liba2.so.0.0.0" 
"liba2.so.0")
libtool: link: (cd ".libs" && rm -f "liba2.so" && ln -s "liba2.so.0.0.0" 
"liba2.so")
libtool: link: ( cd ".libs" && rm -f "liba2.la" && ln -s "../liba2.la" 
"liba2.la" )
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp liba2.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba2.la
libtool: install: cp .libs/liba2.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba2.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba2.so.0.0.0 liba2.so.0 || { rm -f liba2.so.0 && ln -s liba2.so.0.0.0 
liba2.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba2.so.0.0.0 liba2.so || { rm -f liba2.so && ln -s liba2.so.0.0.0 
liba2.so; }; })
libtool: install: cp .libs/liba2.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba2.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ for i in 1 1dep 2 2dep 3 3dep
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba2dep.la a.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
libtool: link: gcc -shared  .libs/a.o      -Wl,-soname -Wl,liba2dep.so.0 -o 
.libs/liba2dep.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba2dep.so.0" && ln -s 
"liba2dep.so.0.0.0" "liba2dep.so.0")
libtool: link: (cd ".libs" && rm -f "liba2dep.so" && ln -s "liba2dep.so.0.0.0" 
"liba2dep.so")
libtool: link: ( cd ".libs" && rm -f "liba2dep.la" && ln -s "../liba2dep.la" 
"liba2dep.la" )
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp liba2dep.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba2dep.la
libtool: install: cp .libs/liba2dep.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba2dep.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba2dep.so.0.0.0 liba2dep.so.0 || { rm -f liba2dep.so.0 && ln -s 
liba2dep.so.0.0.0 liba2dep.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba2dep.so.0.0.0 liba2dep.so || { rm -f liba2dep.so && ln -s 
liba2dep.so.0.0.0 liba2dep.so; }; })
libtool: install: cp .libs/liba2dep.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba2dep.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ for i in 1 1dep 2 2dep 3 3dep
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba3.la a.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
libtool: link: gcc -shared  .libs/a.o      -Wl,-soname -Wl,liba3.so.0 -o 
.libs/liba3.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba3.so.0" && ln -s "liba3.so.0.0.0" 
"liba3.so.0")
libtool: link: (cd ".libs" && rm -f "liba3.so" && ln -s "liba3.so.0.0.0" 
"liba3.so")
libtool: link: ( cd ".libs" && rm -f "liba3.la" && ln -s "../liba3.la" 
"liba3.la" )
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp liba3.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba3.la
libtool: install: cp .libs/liba3.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba3.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba3.so.0.0.0 liba3.so.0 || { rm -f liba3.so.0 && ln -s liba3.so.0.0.0 
liba3.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba3.so.0.0.0 liba3.so || { rm -f liba3.so && ln -s liba3.so.0.0.0 
liba3.so; }; })
libtool: install: cp .libs/liba3.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba3.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ for i in 1 1dep 2 2dep 3 3dep
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba3dep.la a.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
libtool: link: gcc -shared  .libs/a.o      -Wl,-soname -Wl,liba3dep.so.0 -o 
.libs/liba3dep.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba3dep.so.0" && ln -s 
"liba3dep.so.0.0.0" "liba3dep.so.0")
libtool: link: (cd ".libs" && rm -f "liba3dep.so" && ln -s "liba3dep.so.0.0.0" 
"liba3dep.so")
libtool: link: ( cd ".libs" && rm -f "liba3dep.la" && ln -s "../liba3dep.la" 
"liba3dep.la" )
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp liba3dep.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba3dep.la
libtool: install: cp .libs/liba3dep.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba3dep.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba3dep.so.0.0.0 liba3dep.so.0 || { rm -f liba3dep.so.0 && ln -s 
liba3dep.so.0.0.0 liba3dep.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib && { ln -s 
-f liba3dep.so.0.0.0 liba3dep.so || { rm -f liba3dep.so && ln -s 
liba3dep.so.0.0.0 liba3dep.so; }; })
libtool: install: cp .libs/liba3dep.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib/liba3dep.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/broken/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ for withdep in no yes
+ echo

+ echo '### libraries with dependencies: no'
### libraries with dependencies: no
+ rm -rf src /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3
+ mkdir src /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst/bin 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3
+ cd src
+ for i in 1 2 3
+ eval 'ldir=$libdir1'
++ ldir=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib
+ mkdir a1 /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib
+ cd a1
+ case $withdep,$i in
+ echo 'int a1() { return 0; }'
+ /usr/packages/libtool/i686-hades/libtool --mode=compile gcc -g -O2 -c a1.c
libtool: compile:  gcc -g -O2 -c a1.c  -fPIC -DPIC -o .libs/a1.o
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba1.la a1.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib
libtool: link: gcc -shared  .libs/a1.o      -Wl,-soname -Wl,liba1.so.0 -o 
.libs/liba1.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba1.so.0" && ln -s "liba1.so.0.0.0" 
"liba1.so.0")
libtool: link: (cd ".libs" && rm -f "liba1.so" && ln -s "liba1.so.0.0.0" 
"liba1.so")
libtool: link: ( cd ".libs" && rm -f "liba1.la" && ln -s "../liba1.la" 
"liba1.la" )
+ cd ..
+ for i in 1 2 3
+ eval 'ldir=$libdir2'
++ ldir=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib
+ mkdir a2 /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib
+ cd a2
+ case $withdep,$i in
+ echo 'int a2() { return 0; }'
+ /usr/packages/libtool/i686-hades/libtool --mode=compile gcc -g -O2 -c a2.c
libtool: compile:  gcc -g -O2 -c a2.c  -fPIC -DPIC -o .libs/a2.o
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba2.la a2.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib
libtool: link: gcc -shared  .libs/a2.o      -Wl,-soname -Wl,liba2.so.0 -o 
.libs/liba2.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba2.so.0" && ln -s "liba2.so.0.0.0" 
"liba2.so.0")
libtool: link: (cd ".libs" && rm -f "liba2.so" && ln -s "liba2.so.0.0.0" 
"liba2.so")
libtool: link: ( cd ".libs" && rm -f "liba2.la" && ln -s "../liba2.la" 
"liba2.la" )
+ cd ..
+ for i in 1 2 3
+ eval 'ldir=$libdir3'
++ ldir=/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
+ mkdir a3 /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
+ cd a3
+ case $withdep,$i in
+ echo 'int a3() { return 0; }'
+ /usr/packages/libtool/i686-hades/libtool --mode=compile gcc -g -O2 -c a3.c
libtool: compile:  gcc -g -O2 -c a3.c  -fPIC -DPIC -o .libs/a3.o
+ /usr/packages/libtool/i686-hades/libtool --mode=link gcc -g -O2 -no-undefined 
-o liba3.la a3.lo -rpath 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
libtool: link: gcc -shared  .libs/a3.o      -Wl,-soname -Wl,liba3.so.0 -o 
.libs/liba3.so.0.0.0
libtool: link: (cd ".libs" && rm -f "liba3.so.0" && ln -s "liba3.so.0.0.0" 
"liba3.so.0")
libtool: link: (cd ".libs" && rm -f "liba3.so" && ln -s "liba3.so.0.0.0" 
"liba3.so")
libtool: link: ( cd ".libs" && rm -f "liba3.la" && ln -s "../liba3.la" 
"liba3.la" )
+ cd ..
+ test no = yes
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp a1/liba1.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.la
libtool: install: cp a1/.libs/liba1.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib && { ln -s -f 
liba1.so.0.0.0 liba1.so.0 || { rm -f liba1.so.0 && ln -s liba1.so.0.0.0 
liba1.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib && { ln -s -f 
liba1.so.0.0.0 liba1.so || { rm -f liba1.so && ln -s liba1.so.0.0.0 liba1.so; 
}; })
libtool: install: cp a1/.libs/liba1.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ /usr/packages/libtool/i686-hades/libtool --mode=install cp a3/liba3.la 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib/liba3.la
libtool: install: cp a3/.libs/liba3.so.0.0.0 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib/liba3.so.0.0.0
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib && { ln -s -f 
liba3.so.0.0.0 liba3.so.0 || { rm -f liba3.so.0 && ln -s liba3.so.0.0.0 
liba3.so.0; }; })
libtool: install: (cd 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib && { ln -s -f 
liba3.so.0.0.0 liba3.so || { rm -f liba3.so && ln -s liba3.so.0.0.0 liba3.so; 
}; })
libtool: install: cp a3/.libs/liba3.lai 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib/liba3.la
libtool: finish: 
PATH="/usr/packages/libtool/i686-hades/tests:/home/compiler/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/games:/sbin"
 ldconfig -n /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
+ /usr/packages/libtool/i686-hades/libtool --mode=clean rm -f a1/liba1.la 
a3/liba3.la
libtool: clean: rm -f a1/liba1.la a1/.libs/liba1.so.0.0.0 a1/.libs/liba1.so.0 
a1/.libs/liba1.so a1/.libs/liba1.la a1/.libs/liba1.lai
libtool: clean: rm -f a3/liba3.la a3/.libs/liba3.so.0.0.0 a3/.libs/liba3.so.0 
a3/.libs/liba3.so a3/.libs/liba3.la a3/.libs/liba3.lai
libtool: clean: rmdir a1/.libs >/dev/null 2>&1
libtool: clean: rmdir a3/.libs >/dev/null 2>&1
+ test no = yes
+ rm -f 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib/liba3.la
+ echo 'extern int a1(), a2(), a3();
  int main() { return a1() + a2() + a3(); }'
+ gcc -g -O2 -c m.c
+ for st in -static -static-libtool-libs -all-static
+ set +x
./static.at:252: $LIBTOOL --mode=link $CC $CFLAGS $LDFLAGS $st -o m$st 
m.$OBJEXT \
              -L$libdir1 -la1 a2/liba2.la -L$libdir3 -R$libdir3 -la3
Not enabling shell tracing (command contains an embedded newline)
stderr:
stdout:
libtool: link: gcc -g -O2 -o m-static m.o  
-L/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.so 
a2/.libs/liba2.so 
-L/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib -la3 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/src/a2/.libs 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib 
-Wl,-rpath -Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
+ for st in -static -static-libtool-libs -all-static
+ set +x
./static.at:252: $LIBTOOL --mode=link $CC $CFLAGS $LDFLAGS $st -o m$st 
m.$OBJEXT \
              -L$libdir1 -la1 a2/liba2.la -L$libdir3 -R$libdir3 -la3
Not enabling shell tracing (command contains an embedded newline)
stderr:
stdout:
libtool: link: gcc -g -O2 -o m-static-libtool-libs m.o  
-L/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.so 
a2/.libs/liba2.so 
-L/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib -la3 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/src/a2/.libs 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib 
-Wl,-rpath -Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
+ for st in -static -static-libtool-libs -all-static
+ set +x
./static.at:252: $LIBTOOL --mode=link $CC $CFLAGS $LDFLAGS $st -o m$st 
m.$OBJEXT \
              -L$libdir1 -la1 a2/liba2.la -L$libdir3 -R$libdir3 -la3
Not enabling shell tracing (command contains an embedded newline)
stderr:
/usr/bin/ld: attempted static link of dynamic object 
`/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.so'
collect2: ld returned 1 exit status
stdout:
libtool: link: gcc -static -g -O2 -o m-all-static m.o  
-L/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib/liba1.so 
a2/.libs/liba2.so 
-L/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib -la3 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/src/a2/.libs 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst1/lib 
-Wl,-rpath 
-Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst2/lib 
-Wl,-rpath -Wl,/usr/packages/libtool/i686-hades/tests/testsuite.dir/25/inst3/lib
./static.at:252: exit code was 1, expected 0
25. static.at:68:  FAILED (static.at:252)

## ------------- ##
## Test results. ##
## ------------- ##

ERROR: 1 test was run,
1 failed unexpectedly.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##

Please send `tests/testsuite.log' and all information you think might help:

   To: <address@hidden>
   Subject: [libtool 2.2] testsuite: 25 failed

make: *** [check-local] Error 1


> Thanks.
>
>> Test 64 doesn't seem to have any failure details in the log at all.
>
> Oh it does.  Test 64 reruns a number of the other tests with low
> max_cmd_len set, it just sees the failures of 24 and 25 again.

Ah! It might be nice if testsuite.log reported that, but I can't
think of a way of doing that without bloating it up even more than
it already is :)

-- 
`The rest is a tale of post and counter-post.' --- Ian Rawlings
                                                   describes USENET