[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
libtool does not read LIBRARY_PATH
From: |
Samuel Thibault |
Subject: |
libtool does not read LIBRARY_PATH |
Date: |
Mon, 11 May 2009 15:02:16 +0200 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
Hello,
While linking in a msys/mingw32/windows environment, libtool tells me
*** Warning: linker path does not have real file for library -lfoobar.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libfoobar but no candidates were found. (...for file magic test)
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.
*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
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.
Samuel
- libtool does not read LIBRARY_PATH,
Samuel Thibault <=
Re: libtool does not read LIBRARY_PATH, Ralf Wildenhues, 2009/05/11