On 28/03/11 12:23, Mat Booth wrote: > On 28 March 2011 12:08, Andrew Haley <aph@xxxxxxxxxx> 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? > > 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 :-/ I think autotools has done this since the year dot. It's not going to change now. > Either way, I expect the default settings to just work. This isn't just a Fedora problem. Finding JNI libraries is a PITA in general, and patching OpenJDK to do something different from every other JRE isn't a good idea. I'm not at all sure it makes sense to fix this locally in Fedora. We'd want to make sure this is fixed for all GNU/ Linux systems, everywhere. Andrew. -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
