RPATHS in binaries
kelly.ohair at oracle.com
Fri Jul 20 18:27:36 UTC 2012
On Jul 20, 2012, at 1:17 AM, Andrew Haley wrote:
> On 07/20/2012 03:58 AM, Kelly O'Hair wrote:
>> I think Kumar Srinivasan would be the best person to answer if
>> adding a $ORIGIN/../lib/<arch> RPATH entry to jre/bin/java would be
>> an issue or not. I suspect it is not an issue.
> As in "it is not a problem" ? I sometimes have problems reading
> American, although I'm mostly bilingual these days. :-)
Not a problem. As in harmless. :-)
But when people see this RPATH, they will not associate any reasons for it being there.
We need a comment that says "We need this for JAWT and 3rd party shared libraries" or something like that.
Technically, a shared library that has a dependency on something should have itself be dependent
on that library and have an RPATH to locate it. But I understand the difficulty here, the jdk location
is not in a fixed location in general, and having a 3rd party shared library be dependent on a particular
jdk location makes the 3rd party library implementation difficult.
The only other solution I see is for the 3rd party library to have an RPATH of $ORIGIN, and then toss
the 3rd party library into the jdk's jre/lib/<arch> directory (or a softlink to it).
Or maybe into jre/lib/<arch>/thirdparty with an RPATH $ORIGIN/..
But that means modifying the jdk install area, which is sometimes not a good idea.
More information about the build-dev