emerge -u kdevelop failed with checking for KDE >= 3.4.0... configure: error: Installed KDE needs to be version 3.4.0 or later !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-util/kdevelop-3.5.3/work/kdevelop-3.5.3/config.log Digging throug the configure log, I found out, that the ebuild tryed to fetch in kde4 includes (now installed by default to /usr/include/) : configure:33168: checking for KDE >= 3.4.0 configure:33219: i686-pc-linux-gnu-g++ -c -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -march=prescott -O2 -pipe -fomit-frame-pointer -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/qt/3/include -I/usr/include -DQT_THREAD_SUPPORT -D_REENTRANT conftest.cpp >&5 In file included from /usr/include/kdecore_export.h:24, from /usr/include/kdeversion.h:30, from conftest.cpp:46: /usr/include/kdemacros.h:162:29: error: QtCore/qglobal.h: No such file or directory configure:33225: $? = 1 configure: failed program was: adding following line in the src_compile() section solved the problem for me : # Explicitly set kde3.5 include directory myconf="${myconf} --includedir=/usr/kde/3.5/include/" As this is (at least to me ;-)) is an ebuild bug, a similar line should be added to the ebuild Reproducible: Always
Thanks for the report, assigning to maintainers
If KDE 4.1 would be included in the main unstable tree, this bug would hit a lot more users. Thus it should be a blocker for bug #234773. (Can you, Janosch, or a maintainer please update this?)
Please update to the latest versions of kdelibs and kdebase-startkde for both 3.5 and 4.1 versions and try again.
Still does not work with following packages: [U] dev-util/kdevelop (3.5.2-r1@25/06/08 -> (~)3.5.3) [I] kde-base/kdebase-startkde (4.1.2-r1(4.1)@05/10/08) [I] kde-base/kdelibs (3.5.10-r1(3.5)@07/10/08 4.1.2-r1(4.1)@12/10/08)
(In reply to comment #3) > Please update to the latest versions of kdelibs and kdebase-startkde for both > 3.5 and 4.1 versions and try again. > What has kdebase-startkde to do with this? I don't have it installed for any of the versions, in fact for kde-3 I only have installed kdelibs and a couple of other libs required by 3rd party apps. Installed versions are: kde-base/kdelibs-3.5.10-r2:3.5 kde-base/kdelibs-4.1.2-r1:4.1
(In reply to comment #5) > (In reply to comment #3) > > Please update to the latest versions of kdelibs and kdebase-startkde for both > > 3.5 and 4.1 versions and try again. > > > > What has kdebase-startkde to do with this? I don't have it installed for any of > the versions, in fact for kde-3 I only have installed kdelibs and a couple of > other libs required by 3rd party apps. Installed versions are: > kde-base/kdelibs-3.5.10-r2:3.5 > kde-base/kdelibs-4.1.2-r1:4.1 > err, I have kde-base/kdebase-startkde-4.1.2-r1 installed also.
Still does not work after kdelibs:3.5 update: [U] dev-util/kdevelop (3.5.2-r1@25/06/08 -> (~)3.5.3) [I] kde-base/kdebase-startkde (4.1.2-r1(4.1)@05/10/08) [I] kde-base/kdelibs (3.5.10-r2(3.5)@12/10/08 4.1.2-r1(4.1)@12/10/08)
I can confirm this bug with kdelibs-4.1.2-r1, trying to emerge kdevelop-3.5.3 for the first time (not an upgrade). I'll try installing kdebase-startkde but it isn't a dependency of the ebuild.
*** Bug 242086 has been marked as a duplicate of this bug. ***
I hit the same issue trying to upgrade kdevelop from 3.5.2-r1 to 3.5.3 using the latest versions of kdelibs and startkde ~ $ equery list kdelibs [ Searching for package 'kdelibs' in all categories among: ] * installed packages [I--] [ ~] kde-base/kdelibs-3.5.10-r2 (3.5) [I--] [M~] kde-base/kdelibs-4.1.2-r1 (4.1) ~ $ equery list startkde [ Searching for package 'startkde' in all categories among: ] * installed packages [I--] [ ~] kde-base/kdebase-startkde-3.5.10-r4 (3.5) [I--] [M~] kde-base/kdebase-startkde-4.1.1 (4)
Playing around with the configure script revealed that the configuration succeeds if the --prefix parameter is set to the KDE 3.x directory, e.g /usr/kde/3.5 In this case, include and library paths are set to this prefix and the correct headers are used. Thus, to fix the bug KDevelop has to be installed into /usr/kde/3.5 or the configure script has to be patched to set the paths accordingly. Given that nobody uses KDE 3.4 or earlier (I assume) and there won't be a 3.6, the most simple solution would be to install KDevelop officially into /usr/kde/3.5, although it is not a part of KDE 3.5 per se. Given that there will be KDevelop for KDE4, this solution may avoid problems in the future, too. BTW, I guess KDevelop would compile fine if KDE4 would have been installed into its own prefix such as /usr/kde/4.x...
Setting the --prefix=/usr/kde/3.5 in configure worked for me too. I have kdelibs-3.5.10-r2 and kdelibs-4.1.2-r1 installed. Workaround: In the ebuild change: myconf="--with-kdelibsdoxy-dir=${KDEDIR}/share/doc/HTML/en/kdelibs-apidocs" To: myconf="--prefix=/usr/kde/3.5 --with-kdelibsdoxy-dir=${KDEDIR}/share/doc/HTML/en/kdelibs-apidocs" Run: ebuild kdevelop-3.5.3.ebuild manifest emerge -av kdevelop (In reply to comment #11) > Playing around with the configure script revealed that the configuration > succeeds if the --prefix parameter is set to the KDE 3.x directory, e.g > /usr/kde/3.5 > In this case, include and library paths are set to this prefix and the correct > headers are used. > Thus, to fix the bug KDevelop has to be installed into /usr/kde/3.5 or the > configure script has to be patched to set the paths accordingly. Given that > nobody uses KDE 3.4 or earlier (I assume) and there won't be a 3.6, the most > simple solution would be to install KDevelop officially into /usr/kde/3.5, > although it is not a part of KDE 3.5 per se. Given that there will be KDevelop > for KDE4, this solution may avoid problems in the future, too. > > BTW, I guess KDevelop would compile fine if KDE4 would have been installed into > its own prefix such as /usr/kde/4.x... >
better workaround is to use the EXTRA_ECONF option. EXTRA_ECONF="--prefix=/usr/kde/3.5" emerge kdevelop better than patching the ebuild :)
I would say that the more appropriate command would be: EXTRA_ECONF="--prefix=/usr/kde/3.5 --datadir=/usr/kde/3.5/share --sysconfdir=/usr/kde/3.5/etc" emerge kdevelop Otherwise you get no project options when you try to create a new project because some files go to /usr/kde/3.5 and some in /usr.
> EXTRA_ECONF="--prefix=/usr/kde/3.5 --datadir=/usr/kde/3.5/share > --sysconfdir=/usr/kde/3.5/etc" emerge kdevelop I tried this running ~amd64 and KDE 4.1.3 and while kdevelop did compile, it still crashes when attempting to bring up a list of project types. The desktop links also didn't include its path in /usr/kde/3.5.
Problem persists with kdevelop-3.5.4.
(In reply to comment #15) > > EXTRA_ECONF="--prefix=/usr/kde/3.5 --datadir=/usr/kde/3.5/share > > --sysconfdir=/usr/kde/3.5/etc" emerge kdevelop > > I tried this running ~amd64 and KDE 4.1.3 and while kdevelop did compile, it > still crashes when attempting to bring up a list of project types. The desktop > links also didn't include its path in /usr/kde/3.5. > I retried the above command with the new 3.5.4 ebuild and it works here. I'll attach the filelist that I get when I run 'equery f kdevelop'. The kdevelop icon shouldn't appear in the kde4 menu as it gets added to the 3.5 menu directory. Otherwise it works just fine.
Created attachment 177686 [details] kdevelop filelist after EXTRA_ECONF
I have the same problem here with kdevelop-3.5.4, kde-4.1.3 and i686: checking for KDE >= 3.4.0... configure: error: Installed KDE needs to be version 3.4.0 or later !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-util/kdevelop-3.5.4/work/kdevelop-3.5.4/config.log * * ERROR: dev-util/kdevelop-3.5.4 failed. Did anybody tried to set the kdeprefix USE flag to solve the problem?
EXTRA_ECONF="--prefix=/usr/kde/3.5" emerge kdevelop Worked for me! Thanks guys.
net-im/twinkle-1.3.1 suffers from the same issue here, it seems...
Created attachment 179619 [details] Build log of net-im/twinkle-1.3.1 failing very similarly
net-im/twinkle-1.4 has the exact same problem. Someone seems to have broken the kde-3 buildscripts somehow, since they not at all respect --with-extra-includes=/usr/kde/3.5/include anymore. Can someone please update the summary? "kde-3 buildsystems try to include kde-4 includes", or similar.
fixed in kde3 overlay, it will hit the tree in the next days (with the new eclasses as well)
