Instead of adding a symlink I created a file called
/etc/ld.so.conf.d/java.conf which contained :
/usr/lib/jvm/java-6-sun-1.6.0.13/jre/lib/amd64/server/
That was enough to get the library resolved.
Should it be the Java packages fixing this ? I would have thought that
they would be using the
For me, on jaunty 64bit, it was
sudo ln -s /usr/lib/jvm/java-6-sun/jre/lib/amd64/server/libjvm.so
/usr/lib/libjvm.so
(with java-6-sun instead of java-6-sun-1.6.0.12)
Why is that needed? Is there anything wrong with adding that link
manually?
--
Jaunty soprano-backend-sesame2 fails to load
sudo ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so
/usr/lib/libjvm.so
or
sudo ln -s /usr/lib/jvm/java-6-sun-1.6.0.12/jre/lib/amd64/server/libjvm.so
/usr/lib/libjvm.so
works fine in my system (jaunty 64bit)
--
Jaunty soprano-backend-sesame2 fails to load
Thanks for your link Sam Rog.
Since I have a 64Bit-system I had to use a different linklocation to get it
working.
ln -s /usr/lib/jvm/java-6-sun-1.6.0.12/jre/lib/amd64/server/libjvm.so
/usr/lib/libjvm.so
PS: Maybe some other 64bit users should conform this workaround... :-D
--
Jaunty
With the Jaunty/9.04, soprano-backend-sesame_2.2.1-0ubuntu1. i386
ldd /usr/lib/soprano/libsoprano_sesame2backend.so is telling: libjvm.so
= not found
but locate locate libjvm.so is telling:
/usr/lib/gcj-4.3-90/libjvm.so
/usr/lib/jvm/java-1.5.0-gcj-4.3-1.5.0.0/jre/lib/i386/client/libjvm.so
So is this a java packaging bug or still a sesame bug?
--
Jaunty soprano-backend-sesame2 fails to load
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
