In my thoughts this is a problem, which shall be decided by the JVM packagers. libjvm.so is also in the gcj package.
Somehow either - the way sesame accesses libjvm.so shall change, e.g. by loading on-demand. Building it by hand using cmake and the source package; the lib automatically gets the path to libjvm.so inserted (by using the ld rpath option). so it seems like libjvm.so lies at /usr/lib (or somewhere in the path) on the build machine already. - sun jvm / gcc jvm shall publish their lib-path to /etc/ld.so.conf If the sesame-plugin would add /etc/ld.so.conf/ path for itself; this would just be a dirty workaround. -- soprano-backend-sesame requires missing /usr/lib/libjvm.so https://bugs.launchpad.net/bugs/334186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
