On Mittwoch 28 Januar 2009, Tomas Linhart wrote: > Hello all, > > I've decided to try out KDE 4.2. I unmasked all the packages that I > needed, but when I was emerging kde-base/ksysguard I got the following > error: > > Linking CXX shared library ../../lib/libkdeinit4_ksysguard.so > [ 98%] Built target kdeinit_ksysguard > Scanning dependencies of target ksysguard > [100%] Building CXX object > ksysguard/gui/CMakeFiles/ksysguard.dir/ksysguard_dummy.o > Linking CXX executable ksysguard > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to > `QByteArray::indexOf(char const*, int) const' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to > `QPainter::drawPixmap(QPointF const&, QPixmap const&)' > collect2: ld returned 1 exit status > make[2]: *** [ksysguard/gui/ksysguard] Error 1 > make[1]: *** [ksysguard/gui/CMakeFiles/ksysguard.dir/all] Error 2 > make: *** [all] Error 2 > /usr/libexec/paludis/utils/emake: emake returned error 2 > > !!! ERROR in kde-base/ksysguard-4.2.0: > !!! In cmake-utils_src_make at line 1409 > !!! Make failed! > > !!! Call stack: > !!! * cmake-utils_src_make > (/var/tmp/paludis/kde-base-ksysguard-4.2.0/temp/loadsaveenv:1409) > !!! * kde4-base_src_make > (/var/tmp/paludis/kde-base-ksysguard-4.2.0/temp/loadsaveenv:3760) > !!! * kde4-meta_src_compile > (/var/tmp/paludis/kde-base-ksysguard-4.2.0/temp/loadsaveenv:3997) > !!! * src_compile > (/var/tmp/paludis/kde-base-ksysguard-4.2.0/temp/loadsaveenv:5071) > !!! * ebuild_f_compile (/usr/libexec/paludis/2/src_compile.bash:54) > !!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:482) > !!! * main (/usr/libexec/paludis/ebuild.bash:498) > > diefunc: making ebuild PID 3618 exit with error > die trap: exiting with error. > > > I didn't see any other error during the merge. > > The same error occurred when emerging kde-base/ksmserver. > > I tried to re-emerge qt-* packages but the error remains the same. > > Does somebody have a idea what could be wrong?
re-emerge the qt packages in the right order. then emerge kdelibs again, then the rest. Stuff like this happens when qt is updated after kdelibs is built against it.
