Re: libtool does not read LIBRARY_PATH

[Andreas Schwab]

Samuel Thibault <address@hidden> writes:

> Andreas Schwab, le Mon 11 May 2009 19:29:05 +0200, a écrit :
>> Samuel Thibault <address@hidden> writes:
>> > Bob Friesenhahn, le Mon 11 May 2009 11:55:19 -0500, a écrit :
>> >> On Mon, 11 May 2009, Samuel Thibault wrote:
>> >> >but the thing is: LIBRARY_PATH does contain libfoobar.a. Setting LDFLAGS
>> >> >to "-L/where/libfoobar.a/is" makes the problem go away.  It looks like
>> >> >libtool is not taking LIBRARY_PATH into account.  It should.
>> >> 
>> >> I have never heard of LIBRARY_PATH before.
>> >
>> > Err, it is even mentioned in libtool...
>> 
>> Are you using BeOS? :-)
>
> ?!

BeOS is the only system known to libtool that uses LIBRARY_PATH where
most others use LD_LIBRARY_PATH.

> in my m4/libtool.m4 it's in
>
> if test "$GCC" = yes; then
>   variables_saved_for_relink="$variables_saved_for_relink GCC_EXEC_PREFIX 
> COMPILER_PATH LIBRARY_PATH"
> fi

I'd guess BeOS would prefer to use a different name here if it would get
a gcc port.

Andreas.

-- 
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."