Summary: | kde-config --prefix outputs no prefix, can't compile KDE 3.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ivan Savcic <imp> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ivan Savcic
2005-03-22 13:58:41 UTC
Can you guess why you have "/bin/kde-config/"? (instead of /usr/kde/3.4/bin/kde-config) Was all of kdelibs installed in / instead of /usr/kde/3.4, or that file was there before? Gregorio: > Can you guess why you have "/bin/kde-config/"? (instead of > /usr/kde/3.4/bin/kde-config) I just noticed that when you mentioned it now. I have no idea! > Was all of kdelibs installed in / instead of /usr/kde/3.4, or that file was > there before? It seems so. There's no /usr/ prefix for all the kdelibs files. I have packed the contents of my entire /var/db/pkg/kde-base/kdelibs dir here: http://default.co.yu/~imp/files/kdelibs-3.4.0.tar.bz2 It seems that you have an old copy of kde-functions.eclass (in a overlay?) Can you confirm? Gregorio, Yes, it was there. I deleted it, trying to emerge again. Will report in half an hour or so... To be specific, it was in my overlay. Gregorio, It worked! You pinpointed the exact problem, thank you! Now, how should I mark this "bug"? ...invalid, because we are not responsible for tinkering with eclasses. This happened because I used KDE meta-ebuilds before, for previous version of KDE. New ebuilds should ignore this in overlay and use their corresponding eclasses instead, shouldn't they? Well, the fact is that portage does not have the concept of "corresponding eclasses". Interestingly this bug was known by "nearly everyone", but the portage devs. -> http://thread.gmane.org/gmane.linux.gentoo.devel/25513 In general even if this issue wouldn't exist, you can face all sorts of problems with changed inherited stock eclasses. You should _always_ copy and rename all eclasses and their references in your ebuilds. Or to be more clear: eclass overlays are I'm_fine_to_break_my_box stuff. |