bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool make check bug


From: Ralf Wildenhues
Subject: Re: libtool make check bug
Date: Sun, 30 Sep 2007 23:51:39 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Rafael,

* Rafael De Jesus wrote on Wed, Sep 26, 2007 at 07:18:33PM CEST:
> While doing a make check I got the following error(see below).  Can
> someone tell me how to proceed?
[...]
> FAIL: hardcode.test
[...]
> ====================================
> 1 of 112 tests failed
> Please report to address@hidden
> ====================================

* Rafael De Jesus wrote on Wed, Sep 26, 2007 at 08:59:51PM CEST:
> === Running hardcode.test
> = Running make hardcode in ../demo
> You may ignore any linking errors from the following command:
> gcc -g -O2  -o hc-direct main.o ./.libs/libhello.so  -lm -Wl,+b
> -Wl,/home/rdejes
> us/libtool-1.5.24/tests/_inst/lib || echo unsupported > hc-direct
> gcc -g -O2  -o hc-libflag main.o -Wl,+b
> -Wl,/home/rdejesus/libtool-1.5.24/demo/.
> libs -L/home/rdejesus/libtool-1.5.24/tests/_inst/lib -lhello  -lm
> You may ignore any linking errors from the following command:
> LD_LIBRARY_PATH=./.libs gcc -g -O2  -o hc-libpath main.o -lhello  -lm
> -Wl,+b -Wl
> ,/home/rdejesus/libtool-1.5.24/tests/_inst/lib || echo unsupported >
> hc-libpath
> gcc -g -O2  -o hc-minusL main.o -L./.libs -lhello  -lm -Wl,+b
> -Wl,/home/rdejesus
> /libtool-1.5.24/tests/_inst/lib || echo unsupported > hc-minusL
> = 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
> .libs was hardcoded in `hc-libflag', as libtool expected
> .libs was not hardcoded in `hc-minusL', as libtool expected
> FAIL: hardcode.test

Thanks for the reports.  I assume both mails deal with the same system?
Which is it?  What compiler?  Please post the output of
  ./libtool --config

What's really weird about the above output is that there should be a
message about some hardcoding that `fooled libtool'.  Was there maybe a
| `hc-libpath' was not linked properly, which fooled libtool

or similar near the end of the output (on stderr), that got lost on the
way?

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]