Re: Linking with relocated libraries

On Thu, 2004-02-05 at 19:18, psmith@xxxxxxx wrote:

Sorry about the late reply, but here goes...

> I have a situation where I'm constructing a filesystem image, and I need
> to use the contents of that image to build new packages to be installed
> in the image.  For example, I have $ROOT, which might be something like
> /usr/local/images or whatever.
*snip*
> When I'm building packages to be placed into that image, I need to link
> with libraries in $ROOT/usr/lib (for example), but at runtime those
> libraries will be at /usr/lib.
*snip*
> Note how the path to glib can been changed from -lglib, to
> "/usr/lib/libglib.so", ignoring my -L setting.  And of course, this is
> the wrong one so it fails.
> 
This is exactly the same problem reported by Markus Diesmann, fixed by
the patch I've just mailed to -patches.

In summary: it was ignoring the -L when finalising the library paths.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

signature.asc
Description: This is a digitally signed message part

_______________________________________________
Libtool mailing list
Libtool@xxxxxxx
http://mail.gnu.org/mailman/listinfo/libtool