[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libtool wrapper scripts and LD_LIBRARY_PATH

From: Claudio Saavedra
Subject: libtool wrapper scripts and LD_LIBRARY_PATH
Date: Thu, 22 Feb 2018 15:03:44 +0200


This was somewhat asked here [1] and perhaps earlier, but I'm not
entirely sure it has been fully addressed yet.

Premise is a library A that I have modified and installed in a non-
system prefix that is also installed in the system prefix. Now I have
some tests for another library B that depend on the changes I have made
in library A.

These tests for B are using libtool wrapper scripts, so that they can
run against the uninstalled changes of the library they belong to.
However, the wrapper scripts forcefully insert my system path to
LD_LIBRARY_PATH before my own LD_LIBRARY_PATH, which includes the non-
system prefix that I am using. Therefore, library A is loaded from the
system instead of my non-system prefix, unmodified.

The only way I have been able to work this around (without having to
install my changes to A in the system prefix or uninstall A altogether)
is to remove the system prefix from the generated wrapper script by
hand. That works as long as I don't regenerate the scripts, which
happens during distcheck, so this is not a good solution. I don't
really need the system prefix to be in LD_LIBRARY_PATH, and specially,
I don't need it to be included before the contents of my environment-

I looked at build-aux/ where the script template is. The
relevant excerpt is

    # Add our own library path to $shlibpath_var

So I'm guessing that this has something to do with the value of rpath,
but beyond that I have no idea. Both libraries use libtool and



ps. please keep me in cc as I'm not subscribed.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]