Summary: | dev-libs/soprano-2.4.4 breaks while compiling virtuoso backend (amd64 version) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefano Priore <stefano.priore> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | java |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | soprano-2.4.4 build.log |
Description
Stefano Priore
2011-01-07 10:59:42 UTC
Created attachment 259126 [details]
soprano-2.4.4 build.log
This more or less *is* a dupe of your other bug. The problem is still the same - for some reason, soprano is led to to believe that /usr/lib/libjvm.so exists. That should actually be ${JAVA_HOME}/jre/lib/${libarch}/server/libjvm.so (for sun-jdk, atleast and the last part for you will probably be amd64). Actually these files exist on my systems! On the x86 box /usr/lib/libjvm.so is linked to /opt/icedtea6-bin-1.8.1/jre/lib/i386/server/libjvm.so while on the amd86 machine /usr/lib64/libjvm.so is linked to > /opt/sun-jdk-1.6.0.20/jre/lib/amd64/server/libjvm.so After re-reading your comment, I've realized that I've forgot to mention when I posted my reports: both packages compiled fine the first time I installed them (and that should explain why libjvm.so exists). Since the error occurred in both circumstances after having issued `emerge -ve system`, I have to conclude that the problem is not entirely in soprano-2.4.4. Hope this helps pinpointing the cause of the problem... The most likely reson of the problem is the very existence of /usr/lib/libjvm.so. Why did you create those links ? If that was not you, any ideas what did ? Of course I didn't create them... Maybe they're the remnants of older Java installations? Does java-check-environment as root give any hints ? Do those links belong to a package ? If not, can you simply remove them ? java-config-check reports everything's OK. The links don't seem to belong to any package (at least `equery belongs /usr/lib/libjvm.so` reports so) I don't want to remove them without knowing what I'm doing... Without a working crystal ball, it's hard to tell (I still suspect them to be a result of your own actions). That they don't seem to belong to any package, is probably a good enough hint in this case. Remove them and see if things will work as they should. |