Re: ltconfig (GNU libtool) 1.3.5 (1.385.2.206 2000/05/27 11:12:27)

[Michael Long]

The first problem is m4...by default tru64 unix has /bin/m4. Even if you 
install GNU m4 (in /usr/local/bin), it still looks at /bin/m4 first. I 
couldn't find a way around it (other than to remove /bin/m4).  This looks 
like an autoconf issue...and I doubt it will ever be fixed.

The second issue is it would not make libtool.texi even though i had 
installed texinfo...so rather than screw with that I just took "doc" out of 
the makefile.

After those two changes, all the tests pass except hardcode:
FAIL: hardcode.test
324050:.libs/lt-hell: /sbin/loader: Error: Unresolved symbol in 
.libs/lt-hell: n
othing
324050:.libs/lt-hell: /sbin/loader: Error: Unresolved symbol in 
.libs/lt-hell: f
oo
324050:.libs/lt-hell: /sbin/loader: Fatal Error: this executable has 
unresolvabl
e symbols


address@hidden tests]# ./hardcode.test
=== Running hardcode.test
= Running make hardcode in ../demo
You may ignore any linking errors from the following command:
cc -g  -o hc-direct main.o ./.libs/libhello.so  -lm  || echo unsupported > 
hc-di
rect
echo unsupported > hc-libflag
You may ignore any linking errors from the following command:
LD_LIBRARY_PATH=./.libs cc -g  -o hc-libpath main.o -lhello  -lm  || echo 
unsupp
orted > hc-libpath
ld:
Can't locate file for: -lhello
cc -g  -o hc-minusL main.o -L./.libs -lhello  -lm  || echo unsupported > 
hc-minu
sL
= Finding libtool.m4's guesses at hardcoding values
= Searching for hardcoded library directories in each program
.libs was not hardcoded in `hc-direct', as libtool expected
`hc-libflag' was not linked properly, which fooled libtool
`hc-libpath' was not linked properly, as libtool expected
.libs was not hardcoded in `hc-minusL', as libtool expected



--On Sunday, October 15, 2000 11:13 PM -0200 Alexandre Oliva 
<address@hidden> wrote:

> On Oct 15, 2000, Michael Long <address@hidden> wrote:
>
> > Hi..yeah I ran bootstrap. I'm using automake 1.4. I removed missing, but
> > no apparent change.
>
> There was a change: it stopped complaining `missing' doesn't support
> `--run'.
>
> [...]
> > configuring in libltdl
> > running /bin/ksh ./configure  --enable-ltdl-install
> > --cache-file=/dev/null --srcdir=.
>
> Is that all?  There's something wrong with the configuration of
> libltdl.  Could you please run the command line above within libltdl,
> and try to figure out what's going wrong?  Thanks in advance!
>
> --
> Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer                  address@hidden, redhat.com}
> CS PhD student at IC-Unicamp        address@hidden, gnu.org}
> Free Software Evangelist    *Please* write to mailing lists, not to me




Michael Long
Senior Systems Analyst
Info Avenue Internet Services, LLC