Re: libtool-1.15.23b (i386-unknown-freebsd4.3) check results

[David Fang]

> >     Here are my results for libtool-1.15.23b on
> > i386-unknown-freebsd4.3 (most PASSes omitted):
>
> Hmm, all tests pass for me with i386-unknown-freebsd4.8.
>
> Please rerun the failing tests with VERBOSE=1
> e,g:
> env VERBOSE=1 TESTS='hardcode.test pdemo-conf.test pdemo-make.test
> tagdemo-conf.test tagdemo-make.test tagdemo-exec.test" \
>    gmake check

Hi Peter,

        Done, and attached (bz2).
I had to add some tests that were prerequisites of others.

Some relevant excerpts and notes:

---------->8 snip 8<-----------
= Finding libtool.m4's guesses at hardcoding values
= Searching for hardcoded library directories in each program
.libs was hardcoded in `hc-direct', as libtool expected
.libs was hardcoded in `hc-libflag', as libtool expected
`hc-libpath' was not linked properly, which fooled libtool
.libs was not hardcoded in `hc-minusL', as libtool expected
FAIL: hardcode.test
---------->8 snip 8<-----------


---------->8 snip 8<-----------
/ufs/vlsi/fang/freebsd/bin/bash ./libtool --tag=CC   --mode=link ccache
gcc-3.4.0  -g -O2 -no-undefined -version-info 3:12:1  -o libhello.la -rpath
/tmp_mnt/cancun/home2/fang/local/src/libtool-1.5.23b/i386-freebsd4.3-build/tests/_inst/lib
libhello_la-longer_file_name_hello.lo libhello_la-longer_file_name_foo.lo
libhello_la-longer_file_name_foo2.lo -lm
creating reloadable object files...
creating a temporary reloadable object file: .libs/libhello.la-3.o
g++-3.4.0 -r -o .libs/libhello.la-1.o
.libs/libhello_la-longer_file_name_hello.o

/usr/libexec/elf/ld: cannot find -lm
collect2: ld returned 1 exit status
gmake[3]: *** [libhello.la] Error 1
gmake[3]: Leaving directory
`/tmp_mnt/cancun/home2/fang/local/src/libtool-1.5.23
b/i386-freebsd4.3-build/pdemo'
FAIL: pdemo-make.test
---------->8 snip 8<-----------
But I have:
$ ls -l /usr/lib/libm.*
-r--r--r--    1 root     wheel      274862 Apr 21  2001 /usr/lib/libm.a
lrwxrwxrwx    1 root     wheel           9 Jun  7  2001 /usr/lib/libm.so -> 
libm.so.2
-r--r--r--    1 root     wheel      118928 Apr 21  2001 /usr/lib/libm.so.2
and earlier configure tests found a working -lm,  hmm...


---------->8 snip 8<-----------
=== Running tagdemo-exec.test
Executing uninstalled programs in ../tagdemo
/usr/libexec/ld-elf.so.1: Cannot open "./.libs/libbaz.so"
../../tests/tagdemo-exec.test: cannot execute ../tagdemo/tagdemo
FAIL: tagdemo-exec.test
---------->8 snip 8<-----------
This looks like the same failure I see on my own hello-world demo
project: an installed binary linked to a shlib, still uses a hardcoded
path to the *build* directory, not the install directory.  My efforts to
libtool --mode=install or --mode=finish have failed, and I'm out of ideas
on why re-linking isn't happening.  I'm suspecting something is horked
with my setup...


Some additional notes about my environment:
CC=ccache gcc-3.4.0
CXX=ccache g++-3.4.0
MAKEFLAGS=-j4

g++-3.4.0 is installed in /usr/local/compiler/{bin,lib,...}.
autoconf-2.60
automake-1.9.6

Reading specs from
/usr/local/compiler/lib/gcc/i386-unknown-freebsd4.3/3.4.0/specs
Configured with: ./configure --prefix=/usr/local/compiler
--program-suffix=-3.4.0 --enable-shared --enable-threads=posix
--disable-nls --enable-languages=c,c++,f77
Thread model: posix
gcc version 3.4.0

Let me know if there's more you need.

David Fang
Computer Systems Laboratory
Electrical & Computer Engineering
Cornell University
http://www.csl.cornell.edu/~fang/
        -- (2400 baud? Netscape 3.0?? lynx??? No problem!)

libtool-check.log.bz2
Description: Binary data