This is one of the most pain bugs I've seen recently and it took me ages to get to the core of the problem. It's very closely related to bug 81066. Generally speaking QT3 incorrectly checks for compiler version and reports problems during plugin load. Typical error messages include: >checking if UIC has KDE plugins available... no >configure: error: >you need to install kdelibs first or Conflict in /usr/kde/3.5/lib64/kde3/plugins/designer/kdewidgets.so: Plugin uses incompatible Qt library! expected build key "x86_64 Linux g++-4 full-config", got "x86_64 Linux g++-3.* full-config". Conflict in /usr/qt/3/plugins/designer/libcppeditor.so: Plugin uses incompatible Qt library! expected build key "x86_64 Linux g++-4 full-config", got "x86_64 Linux g++-3.* full-config". It's mainly visible with gcc 4.3.x Reproducible: Always Steps to Reproduce: COMPILER_VERSION=`g++ --version 2>/dev/null`; case "$COMPILER_VERSION" in *2.95.*) COMPILER_VERSION="2.95.*" ;; *3.*) COMPILER_VERSION="3.*" ;; *4.*) COMPILER_VERSION="4" ;; *) ;; esac echo "CURRENT CHECK:" echo "Correct compiler version: `g++ --version | sed q`"; echo "Compiler version reported by configure $COMPILER_VERSION"; COMPILER_VERSION=`g++ -dumpversion 2>/dev/null` case "$COMPILER_VERSION" in 2.95.*) COMPILER_VERSION="2.95.*" ;; 3.*) COMPILER_VERSION="3.*" ;; 4.*) COMPILER_VERSION="4" ;; *) ;; esac echo "PATCHED VERSION:" echo "Correct compiler version: `g++ --version | sed q`"; echo "Compiler version reported by configure $COMPILER_VERSION"; Actual Results: CURRENT CHECK: Correct compiler version: g++ (Gentoo 4.3.2 p1.0) 4.3.2 Compiler version reported by configure 3.* Expected Results: PATCHED VERSION: Correct compiler version: g++ (Gentoo 4.3.2 p1.0) 4.3.2 Compiler version reported by configure 4 This bug was a big blocker for my kde3 application development
Created attachment 170095 [details, diff] Fixes incorrect check That check fixes the problem
Created attachment 170097 [details, diff] Fixes incorrect check It seems I had to add an extra line somewhere in my configure and the previous patch didn't apply properly. This version works well.
Created attachment 170098 [details, diff] third time the charm sorry
*** Bug 236793 has been marked as a duplicate of this bug. ***
Fixed in CVS now
*** Bug 243918 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > Fixed in CVS now > Ben, Personally I think you should bump qt-3.3.8b version to -r1 to make sure everyone who's using qt3 will get an updated version. Leaving it as it is, will cause more problems in the longer run, and people won't know the cause of the problem (some bugs reported and marked as duplicate of this bug because the core of the problem remains - people don't know they need to REINSTALL qt3 after you've updated an ebuild. -r1 will UPDATE it - so everyone who's using qt3 will have a "proper" version). currently: paludis -ip qt:3 (emerge -av qt:3) gives me version: qt-3.3.8b Personally I think it's quite severe bug, that's why I used BLOCKER severity. my 2cents. Regards, Rob
Reopening for the revbump -- users are hitting the bug even after two weeks.
I still have this problem, even after reinstalling both qt-3 and kde-libs-3 several times. Any ideas?
I checked config.log and got this: configure:31150: checking for KDE configure: 31203: /usr/kde/3.5/include/ksharedptr.h taking that configure: 31233: /usr/kde/3.5/lib/libkio.la taking that configure: 31251: /usr/kde/3.5/lib/kde3/plugins/designer/kdewidgets.la taking that configure:31324: result: libraries /usr/kde/3.5/lib, headers /usr/kde/3.5/include configure:31363: checking if UIC has KDE plugins available configure:31390: /usr/qt/3/bin/uic -L /usr/kde/3.5/lib/kde3/plugins/designer -nounload -impl actest.h actest.ui > actest.cpp ./configure: line 31391: 16260 Segmentation fault /usr/qt/3/bin/uic -L /usr/kde/3.5/lib/kde3/plugins/designer -nounload -impl actest.h actest.ui > actest.cpp configure:31393: $? = 139 configure:31407: result: no configure:31418: error: you need to install kdelibs first. If you did install kdelibs, then the Qt version that is picked up by this configure is not the same version you used to compile kdelibs. The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the _same Qt version_, compiled with the _same compiler_ and the same Qt configuration settings.
Okay, it is revbumped now. Are there still any remaining problems?
Using ~amd64 as of today. After installing x11-libs/qt-3.3.8b-r1, the look of my KDE 3.5.10 installation has changed quite a bit: borders around widgets are at least 1px wider, without any interaction on my behalf. I cannot tell for sure, but some of my KDE "styles" may have vanished from kcontrol, too (I cannot recall which Style I was using, but none of those available now match the widget style I'm used to look at). Furthermore, when trying to install kde-base/kdeartwork-styles-3.5.10 now, paludis croaks with this: checking for KDE... libraries /usr/kde/3.5/lib64, headers /usr/kde/3.5/include checking if UIC has KDE plugins available... no configure: error: you need to install kdelibs first. (I'm new to this bug and awfully tired right now, but... isn't that exactly the problem which is supposed to be fixed by this new revision?)
Thats the reason why is ebuild warns this way: elog "After a rebuild of Qt, it can happen that Qt plugins (such as Qt/KDE styles," elog "or widgets for the Qt designer) are no longer recognized. If this situation" elog "occurs you should recompile the packages providing these plugins," elog "and you should also make sure that Qt and its plugins were compiled with the" elog "same version of GCC. Packages that may need to be rebuilt are, for instance," elog "kde-base/kdelibs, kde-base/kdeartwork and kde-base/kdeartwork-styles." elog "See http://doc.trolltech.com/3.3/plugins-howto.html for more infos." echo
*** Bug 263438 has been marked as a duplicate of this bug. ***
This looks fixed.
