Summary: | Failure to emerge kde-base/kdelibs-4.2.2: error in linking "../lib/libkhtml.so" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ashu Tiwary <ashutiwary> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | dliana, Martin.Spoo, rsa4046 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kde-base/kdelibs-4.2.2 build log with parallel make and LDFLAGS="-Wl,--as-needed,-O1,--sort-common"
kde-base/kdelibs-4.2.2 build log without parallel make and LDFLAGS="-Wl,--as-needed,-O1,--sort-common" |
Description
Ashu Tiwary
2009-04-13 05:43:29 UTC
Created attachment 188185 [details]
kde-base/kdelibs-4.2.2 build log with parallel make and LDFLAGS="-Wl,--as-needed,-O1,--sort-common"
Created attachment 188186 [details]
kde-base/kdelibs-4.2.2 build log without parallel make and LDFLAGS="-Wl,--as-needed,-O1,--sort-common"
OK - removing "jpeg2k" from the kde-base/kdelibs USE flags had no impact - same error, in same place. FWIW, those symbols are from media-libs/jpeg Yea -I had tried re-emerging media-libs/jpeg - no effect (kde-base/kdelibs-4.2.2 still failed to emerge - in same place). Does it happen without the --sort-common? Yes, I had tried both w/ my standard LDFLAGS ("-Wl,--as-needed,-O1,--sort-common") as well as without - no difference. Could this be related to ibm-jdk-bin:1.4 ROOTPATH (see bugs http://bugs.gentoo.org/241390, http://bugs.gentoo.org/206895) Added: I had the build error in the identical place as the OP (in kde-base/kdelibs-4.2.2-r1). I use ibm-jdk-bin-1.4.2.13; after commenting out my ROOTPATH statement in /etc/env.d/20java: # ROOTPATH=/opt/ibm-jdk-bin-1.4.2.13/bin:/opt/ibm-jdk-bin-1.4.2.13/jre/bin and of course # env-update && source /etc/profile the ebuild finished successfully ... obviously this is just a work-around, not a real solution, and I don't know if this is even related to OP's issue, but I posted anyway as a possibility. (In reply to comment #8) > Could this be related to ibm-jdk-bin:1.4 ROOTPATH (see bugs > http://bugs.gentoo.org/241390, http://bugs.gentoo.org/206895) > My /etc/env.d/20java contained information about jdk-142 (odd - system vm is/was set to jdk6-13) - I removed the information about jdk142 and replaced it with the (correct) jdk6-13 information (+ env-update, logoff, logon) - and was able to emerge successfully (kde-base/kdelibs-4.2.2-r1) - so, it is not ROOTPATH itself, but specifically, ROOTPATH when set to point to jdk142 (this also appears to be the case as listed in bug #206895 - comment #18 - which I made back in Dec for a different system - I didn't remember that when I opened this bug - and, obviously, didn't search well enough....). I think this should prolly be marked as dup of 206895. Indeed *** This bug has been marked as a duplicate of bug 206895 *** |