Τι γλώσσα είναι ομιλίας σας?
Ezra Peisach wrote:
One of the other misfeatures of rpath is that it sets DT_RPATH and not
DT_RUNPATH - which means that LD_LIBRARY_PATH will not override the
setting... This means if you have a library installed in the RPATH and
you set LD_LIBRARY_PATH (for in tree development - or old installation
and a new tree) you are using the wrong library. This is a magical
option to ld to use DT_RUNPATH - but I do not remember it - but then you
can use LD_LIBRARY_PATH to override... See the ld.so manoage for
DT_RPATH vs RUNPATH....
Ezra
Matt Harrington wrote:
On Thu, May 28, 2009 at 9:45 PM, Johan Hattne
<johan.hat...@utsouthwestern.edu> wrote:
However, I was wondering if there's a better way than to just ignore
this. Perhaps RPATHs could be removed entirely from the upstream
build?
Couldn't this, perhaps, be fixed using for instance chrpath (disclaimer:
I've never used it myself)? I suppose even if the rpaths were removed
by upstream, your problem wouldn't go away.
Yes, that's another workaround I could do at my end of things, but I
was hoping they could be removed entirely from the precompiled
package. I have a feeling they crept in there through autobuild and
probably aren't even required on Paul's development machine. I think
he's away right now, so perhaps we can revisit this in a week or two.
Matt
