On Saturday 21 February 2004 11:31, Pieter Grimmerink wrote:
> There are multiple versions of this library, one in /usr/lib (with a .la
> file), and one elsewhere, without a .la file.
> I need the one elsewhere, because I'm crosscompiling.
> I know I should probably try what happe
On Saturday 21 February 2004 02:24, Kevin P. Fleming wrote:
> Pieter Grimmerink wrote:
> > So I removed the .la script belonging to my library in /usr/lib, libtool
> > does not find it anymore, and now it works.
>
> Are you saying there was a .la file in /usr/lib for a libra
I've downloaded and installed libtool-1.5.2, and tried the same as with my
reports about 1.4.3
It behaves exactly the same, it finds libraries in /usr/lib, instead of where
-L wants them to be found.
Then I replaced
newlib_search_path=" $newlib_search_path"
by
newlib_search_path="$newlib_searc
I've asked for help about this problem twice in the last
few weeks, without any replies.
In the meantime I've done some searching in the libtool
list history, and I came across this:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg04324.html
This seems to be exactly the same problem I'm having.
When crosscompiling an autoconf/automake project, I pass the target's libary
path with "LDFLAGS= -L /compiletarget/lib" as argument for the configure
script.
But now a libtool script is created, that contains the following variable:
sys_lib_search_path_spec="/lib /usr/lib /usr/local/lib"
These
Hi all,
I have a strange situation with libtool (version 1.4.3), I'm wondering what I
could do to make it work.
I'm trying to crosscompile a C++ project on an i686, for a cris architecture
target.
Compiling with libtool goes fine, but linking fails:
../libtool --mode=link --tag=CXX g++-cris -
