If you link against a library that has rpath defined - you will inherit
it in the executable...
So - the following have rpath hardwired in from the autobuild script....
libgreg
libgtkglext-x11
libguile*
libreadline
libhistory
And I do not know which library depends on the others....
So - it is inherited...
Ezra
Kevin Cowtan wrote:
Oh, hang on.
If I do:
objdump -p `which coot-real` | grep RPATH
then I get:
RPATH
/y/people/emsley/autobuild/Linux-bragg1.chem.york.ac.uk-pre-release-gtk2/lib
I can't see where that is coming from, but I'm pretty sure it is
redundant, since that directory doesn't exist on the machine where I
am running the program.
K
Kevin Cowtan wrote:
OK, I understand, RPATH bad.
But as far as I can tell we don't use RPATH. Coot uses
LD_LIBRARY_PATH, which is only set by a wrapper script which launches
the actual binary, and so the use of LD_LIBRARY_PATH is never exposed
to the rest of the system (which I understand is the only problem
with LD_LIBRARY_PATH).
Of course, I have no idea how Coot is being built by downstream
packagers - only how we build our binaries (and I have rather limited
understanding of that - hopefully Paul will be able to comment later
in the week).
K
Matt Harrington wrote:
On Mon, Jun 1, 2009 at 1:14 AM, Kevin Cowtan
<[email protected]> wrote:
Τι γλώσσα είναι ομιλίας σας?
This should shed some light on the subject:
http://en.wikipedia.org/wiki/Rpath_(linking)
Matt
