Summary: | kde-base/kopete-4.1.2 fails to build with useflag jabber: qplatformdefs.h missing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rafael Kolless <rafael> |
Component: | [OLD] KDE | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | coornail, cully.bennefield, jcwren, kde, orodruinlair, pmontepagano, quazgar, vapier, vineus |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
eclass-debug.log environment qt-core log from before qt-core log after |
Description
Rafael Kolless
2008-10-05 00:53:09 UTC
Created attachment 167233 [details]
build.log
Created attachment 167235 [details]
eclass-debug.log
Created attachment 167237 [details]
environment
*** Bug 240373 has been marked as a duplicate of this bug. *** I experienced this as well. When emerged with -jabber it was successful. I received the following message when it was failing: qplatformdefs.h: No such file or directory kde-base/kopete-4.1.2 USE="addbookmarks alias autoreplace contactnotes gadu highlight history latex msn nowlistening oscar otr pipes privacy sms ssl statistics texteffect translator urlpicpreview webpresence winpopup yahoo -debug -groupwise -htmlhandbook -jabber -kdeprefix -messenger -qq -testbed" Linux aero 2.6.24-gentoo-r4 #1 SMP Thu May 15 16:39:03 CDT 2008 i686 Intel(R) Pentium(R) M processor 1400MHz GenuineIntel GNU/Linux Cheers *** Bug 241762 has been marked as a duplicate of this bug. *** It should probably be noted that if you use 'ufed' to manage the USE flags, jabber must be set to [-]. Leaving it blank causes jabber to be included. Yes, if jabber is unset than kopete builds fine but normaly I expect that it builds straight with the useflag and I would like to use Kopete with xmpp. As a "quick and dirty" workaround I copied I /usr/share/qt4/mkspecs/linux-g++/qplatformdefs.h into the correct /usr/share/qt4/qt then the build works. So it seems clearly that the kopete build does not recognize /usr/share/qt/mkspecs as a include folder. My knowledge to cmake is very limited so I don't know currently where this could be fixed. (In reply to comment #8) > As a "quick and dirty" workaround I copied I > /usr/share/qt4/mkspecs/linux-g++/qplatformdefs.h into the correct > /usr/share/qt4/qt sorry for the mistype: I copied it to /usr/include/qt4/Qt > then the build works. I managed to replicate this behavior. It seems that it has some issues qit qt-core older than 4.4.2. Try upgrade on qt-core-4.4.2 and report if it fixes the problem, or just close the bug. Excuse me but qt-core-4.2.2 is installed on my system since I opened this bug: eix qt-core [I] x11-libs/qt-core Available versions: (4) [M](~)4.4.0 (~)4.4.1 (~)4.4.1-r1 (~)4.4.2 {debug doc glib pch qt3support ssl} Installed versions: 4.4.2(4)(19:22:47 03.10.2008)(qt3support ssl -debug -doc -glib -pch) Homepage: http://www.trolltech.com/ Description: The Qt toolkit is a comprehensive C++ application development framework. This can be found in the build.log also: -- Found Qt-Version 4.4.2 (using /usr/bin/qmake) I see no reason to close the bug because an upgrade of qt-core is not possible :) Ok in that case try it with -pch then :]. And i was so happy that i was able to reproduce this :D erm i am again elsewhere when typing... i thought +glib not -pch... Thanks alot Tomas, After rebuilding qt-core with the useflag glib kopete builds with the jabber support successfully. I tried to reproduce the failure again by rebuilding qt-core (and qt-gui) with glib unset but also after this it builded properbly. I made a binary backup of the old qt-core and using this packages I could reproduce the build error. In this case the first built of qt-core-4.4.2 and I tried to find out if ths "faulty" built could be reproduced. For KDE 4.1.2 I switched from stable QT 4,3 to the keyworded QT 4,4 so I downgraded Qt 4.4 to QT 4.3 and rebuilded qt-4.4 with QT 4.3 currently installed. After this downgrading/upgrading process I tried to build kopete 4.1.2 again and the same built error appeared again. It seems that this whole bug is an upgrade issue of QT4. The general solution is just to rebuild qt-core again, the useflag glib is not needed. How could this be fixed in the future? Building qt-core twice during an upgrade of QT? Would you mind creating diff between tghe package installed file and files you have on system wehn you sucesfully compile kopete? Maybe ewen crete diff between files itself so we can see what differ? thanks in advice :] this isnt fixed ... kopete needs a depend on qt-core:glib Well i have whole kde compiled with qt not having glib flag. So i would say that is negative... my point was that this isnt fixed. my saying it needed a glib depend was based on earlier comments. if that isnt the case, then something else is broken ... but that still brings us back to "this bug isnt fixed". i just hit it on my x86_64 machine. as soon as i rebuilt only qt-core with USE=glib, kopete emerged fine. Ok here is the deal. Emerge qt-core without that flag again and you will be still working. It is some issue in updating qt. Try to make diff between first and the last install so we can see what has changed. Maybe we would be able to track this thing down. Created attachment 170531 [details]
qt-core log from before
Created attachment 170533 [details]
qt-core log after
Erm i had on my mind new log also without glibc... I think my last comment is the reason that looks like +glib is needed for it but it also compile without glib if qt-core is not emerged from qt-4.3 directly. For me this upgrade path leads to a build failure in kopete: qt-4.3.3->qt-core-4.4.2-> build error If you remerge qt-4.4.2 no built error appear: qt-4.3.3->qt-core-4.4.2->qt-core-4.4-2-> no build error During my several rebuilds I was able to compile with Jabber support using +glib and -glib. (In reply to comment #15) > Would you mind creating diff between tghe package installed file and files you > have on system wehn you sucesfully compile kopete? > Sorry, I missed your reply. Is there a simple solution to create the diffs? Would like to have a diff of the bin package which it didn't compile correctly? (In reply to comment #24) > (In reply to comment #15) > > Would you mind creating diff between tghe package installed file and files you > > have on system wehn you sucesfully compile kopete? > > > > Sorry, I missed your reply. > > Is there a simple solution to create the diffs? Would like to have a diff of > the bin package which it didn't compile correctly? > just paste here log for qt-core when kopete failed and also paste log when kopete didnt (for qt-core and not using glib flag) *** Bug 250936 has been marked as a duplicate of this bug. *** (In reply to comment #23) > > For me this upgrade path leads to a build failure in kopete: > > qt-4.3.3->qt-core-4.4.2-> build error > > If you remerge qt-4.4.2 no built error appear: > > qt-4.3.3->qt-core-4.4.2->qt-core-4.4-2-> no build error I can confirm that building qt-core twice, both times with "-glib", will fix this problem. Could you provide the build log of qt-core? I still miss my developer system and I tried to reproduce it in a virtual machine but my time currently is extremly limited for this :( The same bug appeared for kopete-4.2 as well. Using qt-core-4.4.2-r1 fixed it though, so maybe this can be closed as well? This was fixed by the magical qt deps which force user to have clean versions. |