On 2011-07-19 13:43, Johannes Pfau wrote:
Jacob Carlborg wrote:
On 2011-07-19 12:33, Johannes Pfau wrote:
Seems like rpath could indeed work in this case. I can't find much
documentation about it though. Debian recommends not to use it:
http://wiki.debian.org/RpathIssue but I'm not sure if this problem
applies to orbit.
Won't the same problem occur if rpath isn't used? With LD_LIBRARY_PATH
for example.
I'm not sure about that, but using LD_LIBRARY_PATH is even more
discouraged (because it propagates to child processes)
Ok. What is used to tell the system where to find a library? Only the
default paths as /usr/lib ?
I'm not sure if we can have one perfect approach for all operating
systems. But we could just use the rpath way and see how it works out.
Yeah. We'll see how it turns out.
I agree that's a nice-to-have feature, but is it ever really necessary?
This mechanism always picks up the newest ABI compatible library
version. Why would you want to specify one version explicitly if the
newer version can be used as a 1:1 replacement?
I don't know if it's really necessary but that's how I've been thinking
that I want it to behave.
--
/Jacob Carlborg
