Excerpts from Mat Booth's message of Mon Mar 28 13:23:00 +0200 2011:
On 28 March 2011 12:08, Andrew Haley <aph(a)redhat.com> wrote:
> On 26/03/11 18:34, Mat Booth wrote:
>> In F14's OpenJDK, the default java.library.path currently does not
>> include /usr/local/lib or /usr/local/lib64 so if a third party JNI
>> library installs itself into one of those directories then the JVM
>> will not know about it.
>>
>> Is this a bug? I think it would be appropriate if /usr/local/lib and
>> /usr/local/lib64 were included in the default java.library.path
>
> I wouldn't have thought so. /usr/local/lib isn't really standard for
> anything. Even if we could patch OpenJDK to do this, the third party
> apps would immediately break with any other JRE.
>
> Doesn't it make more sense for the app to know where its native library
> is, and load it from the right place?
>
> Andrew.
> --
I would rather the app not have to care where the libraries are, but
for some odd reason the autotools in Fedora uses a default prefix of
/usr/local rather than /usr
If this is not a standard location then maybe this is an autotools
bug? I shouldn't have to tell the autotools where it is appropriate to
install things for the operating system it ships with :-/
Either way, I expect the default settings to just work.
I know you already solved your problem, so this is just FYI.
AFAIK autotools always default to /usr/local when doing pure
./configure. Fedora's %configure macro changes --prefix to /usr to
make this correct for us.
So if you are creating some rpm that uses autotools, you'd better use
%configure macro (it sets more things, not just --prefix).
--
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Software Engineer - Base Operating Systems Brno
PGP: 7B087241
Red Hat Inc.
http://cz.redhat.com