On Sat, 21 Feb 2004, Albert Chin wrote:
> > So, basically, it sounds like libtool has reinvented the very annoying
> > Tru64 library search mechanism, where any shared libraries are found
> > before static libraries regardless of the relative order on the library
> > path, except as applied to *.l
* eManager Notification **
Junkmail Notify
Source mailbox: "[EMAIL PROTECTED]"
Destination mailbox(es): "[EMAIL PROTECTED]"
Policy: Misc(via-gra)
Action: Delete
*** End of message ***
--- Begin Message ---
Send Libtool mailing list submissi
On Sat, Feb 21, 2004 at 10:43:22AM -0800, Russ Allbery wrote:
> Pieter Grimmerink <[EMAIL PROTECTED]> writes:
>
> > OK, now I've given the library in -L a .la file as well. Now both
> > libraries have a .la file, and libtool-1.5.2 uses the correct library,
> > in -L. So that's solved then.
>
> S
Pieter Grimmerink <[EMAIL PROTECTED]> writes:
> OK, now I've given the library in -L a .la file as well. Now both
> libraries have a .la file, and libtool-1.5.2 uses the correct library,
> in -L. So that's solved then.
So, basically, it sounds like libtool has reinvented the very annoying
Tru64
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 happens when both have
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 library that is
> _not_ in /u
