Summary: | kde-base/kdelibs tries to link to /opt/ibm-jdk-bin-1.4.2.9/jre/bin/libjpeg.so | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bernhard Frauendienst <gentoo> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | andreas.thalhammer, ashutiwary, christian.korff, corsair, daniel, dirk, dkarasik, flockmock, florian, java, morgoth6 |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 176781 | ||
Bug Blocks: | |||
Attachments: | kdelibs-4.0.0 build.log |
Description
Bernhard Frauendienst
2008-01-21 17:40:56 UTC
Created attachment 141491 [details]
kdelibs-4.0.0 build.log
I think I might have found the problem: if you look at lines 397 and 402 of the build log, the build systems claims to have found the libjpeg.so in /opt/ibm-jdk-bin-1.4.2.9/jre/bin/, which is of course not the file from media-libs/jpeg. I think gen-2 VMs don't change the LD_PATH anymore, but until gen-1 is phased out, this must be fixed otherwise. Actually, to have kdelibs link to the correct libraries, I had to disable the ROOTPATH line in /etc/env.d/20java... LDPATH seemingly was in the right order after all, so meddling with ROOTPATH should be sufficient to fix this bug. (In reply to comment #3) > Actually, to have kdelibs link to the correct libraries, I had to disable the > ROOTPATH line in /etc/env.d/20java... > > LDPATH seemingly was in the right order after all, so meddling with ROOTPATH > should be sufficient to fix this bug. Or moving 20java after 45kde (giving it a higher number). Java any comments on how to resolve this? You sure it wasn't LDPATH? Did you run env-update && source /etc/profile after changing anything in env.d, in the same terminal window that runs emerge? It would be strange if it looked in PATH (i.e. ROOTPATH when emerging with root privs) for libraries. But even if it was, I doubt changing the order of env.d files would help, as I doubt KDE's env file points ROOTPATH to /usr/lib where libjpeg normally is... (In reply to comment #5) I confirm that commenting the ROOTPATH and running env-update && source /etc/profile allows you to compile kdelibs-4.0.0. (In reply to comment #5) > You sure it wasn't LDPATH? Apparently it really is. Another user hit it today and confirmed that removing ibm-jdk from ROOTPATH and changing nothing else fixed it. > It would be strange if it looked in PATH (i.e. ROOTPATH when emerging with > root privs) for libraries. Agreed. I'm going to talk to cmake upstream to figure out if it's really a cmake bug... Thanks. (In reply to comment #7) > Agreed. I'm going to talk to cmake upstream to figure out if it's really a > cmake bug... Thanks. Great. Hopefully the 20java env file will be gone "soon" with the rest of gen-1 :) (In reply to comment #8) It appears that commenting out ROOTPATH from 20java does not allow you to build kdelibs-4.0.0-r1. (In reply to comment #9) > (In reply to comment #8) > It appears that commenting out ROOTPATH from 20java does not allow you to build > kdelibs-4.0.0-r1. Did you run env-update and source /etc/profile after the change? In the exact shell instance that you re-run emerge afterwards? *** Bug 212944 has been marked as a duplicate of this bug. *** I can confirm the commented out ROOTPATH variable in /etc/env.d/20java as a workaround to compile kde-base/kdelibs-4.0.3-r1. My machine is a PowerPC (ppc, 32-bit), IBM JDK is up-to-date 1.4.2, 1.5.0 and 1.6.0 (in 20java the path points to 1.4.2, regardless what system-vm and user-vm I set with java-config). kde-base/kdelibs-4.0.3-r1 fails to compile without this workaround at around 98% on this ~ppc arch. BTW, the same goes at least for kde-base/ark-4.0.3 and kde-base/gwenview-4.0.3. For the remaining 89 ebuild up to and including kde-base/kde-meta:kde-4 (4.0.3) I used the workaround all the way. Greetings, Andreas. Can anyone confirm if this is still happening with the 4.1.2 ebuilds? Happened to me in 4.1.1 few weeks ago. Still happend for 4.1.2-r1 on amd64 here. Commenting ROOTPATH solves the problem. This should be fixed in 4.1.3-r1. Please test. (In reply to comment #17) > This should be fixed in 4.1.3-r1. Please test. > kde-base/kdelibs-4.1.3-r1: still broken (on amd64/x96-64); commenting out ROOTPATH allowed for a successful emerge (actually, I just replaced the IBM 1.4.2r12 env w/ the Sun JDK 6u10 info). still happens with kdelibs-4.2.0-r1 on ~ppc (and installed ibm-jdk-bin:1.4) *** Bug 257916 has been marked as a duplicate of this bug. *** still happens with kdelibs-4.2.2-r1 on ~ppc (and installed ibm-jdk-bin:1.4) jdk:1.4 is obsolete Update java-config-wrapper to 0.16 (~arch yet) run java-check-environment and do what it suggests. When it's stable and bug 176781 is closed, then you could maybe add a check for existence of /etc/env.d/20java to the cmake (or some derived) eclass... *** Bug 241390 has been marked as a duplicate of this bug. *** *** Bug 265945 has been marked as a duplicate of this bug. *** (In reply to comment #23) > Update java-config-wrapper to 0.16 (~arch yet) > run java-check-environment and do what it suggests. As said. |