On Tuesday 11 May 2004 16:01, Konstantinos Georgokitsos wrote:
Ich wollte auf meiner SuSE 8.1. mit KDE 3.2.2 (von SuSE) kmldonkey kompilieren und bin schon beim ./configure auf die Nase gefallen:
kmldonkey-0.10pre3> ./configure --prefix=/opt/kde3 checking build system type... i686-pc-linux-gnu [...] checking for Qt... configure: error: Qt (>= Qt 3.1 (20021021)) (library qt-mt) not found. Please check your installation! For more details about this problem, look at the end of config.log. Make sure that you have compiled Qt with thread support!
./configure --prefix=/opt/kde3 --with-qt-dir=/usr/lib/qt3 macht uebrigens keinen Unterschied. Natuerlich habe ich Qt installiert, bin aber nicht sicher ob SuSE thread support einbindet (nehme es aber an). Ich habe dann mal ./configure eines anderen Projekts ausprobiert (kalbum) und bekam die gleiche Fehlermeldung.
Habe auch frueher oft selbstkompiliert, und habe den Eindruck dieses Problem ist erst nach dem update auf 3.2.2. aufgetreten, bin aber nicht 100% sicher.
Hier noch meine qt-rpms:
<snip>
Bin fuer jeden Hinweis dankbar.
Kostas
(you should post in english, then you get more answers on this list.) I had similar compile errors, however not about "Qt with thread support", but about Qt in general. Depending on how the configure script of kmldonkey is build, this could be also what is causing your error. Have a look at this: The reason for the error I saw was that a certain version of kde's acinclude.m4 or aclocal.m4 ( which you or the one who created the configure script for the app you try to compile probably got in an upgrade) does mess up the generation of the configure file. QUICK FIX: modify your configure script: =========================== 1) look for the line kde_line="$kde_line -impl actest.h actest.ui > actest.cpp" 2) take out: -impl actest.h the line should be now: kde_line="$kde_line actest.ui > actest.cpp" 3) look for "klineedit" and change it to "KLineEdit" The line should be: if test -f actest.cpp && grep KLineEdit actest.cpp > /dev/null; If you develop yourself, and get these errors in your configure scripts build in by autoconf, you need to clean the base scripts for acinclude.m4 or aclocal.m4 somewhere in /opt/kde. Autoconf takes these to build the files for teh app you develop, so once they are cleaned in /opt/kde the error does not get reintroduced when you rerun autoconf. HTH, Matt