Andrew Haley wrote: > Felix Schwarz wrote: >> Andrew Haley schrieb: >>> Felix Schwarz wrote: >>> >>>>> Specifically, "If the JNI-using code calls System.loadLibrary you'll >>>>> have to patch it to use System.load, passing it the full path to the >>>>> dynamic shared object." >>>>> >>>>> For an example of this see >>>>> http://cvs.fedoraproject.org/viewcvs/devel/javasqlite/ >>>> Sorry, my wording was not detailed enough. JCC does "JNI the other way >>>> round" so it calls Java from C++. Therefore there is no >>>> System.loadLibrary which could be patched. Instead I have to rely on the >>>> standard linker configuration (or use rpath). >>> Or use a full path in dlopen(). >> I may be wrong but it seems that JCC does do any dlopens. Instead the code >> is just linked against the Java libraries. I may be wrong on this, though. >> >>> What libraries does JCC need to open? Just libjvm, or others? >> libjava.so and libjvm.so. > > OK, I understand now. I'm going to ping a few of my colleagues to see > what they think we should do. I've pinged. Please open a Bugzilla item and we'll look into adding libjvm.so and its dependencies to /etc/ld.so.conf.d and/or ld.so.cache. This will be in the Fedora 10 timeframe. We'll also have to talk to upstream about this. Thanks, Andrew. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
