PDA

Click to See Complete Forum and Search --> : Cannot detect qt.

h4n9m4n
03-10-2005, 02:48 AM
Right now im trying to install a few things, but they all need qt. so i installed qt3 and qt3-devel via urpmi.
so i go to ./configure, and i get

checking for Qt... configure: error: Qt (>= Qt 2.2.2) (libraries) not found. Please check your installation!

i check the config.log and i find this

/usr/bin/ld: cannot find -lqt

I think that's the problem. ive also tried installing using

./configure --with-qt-libraries=/usr/lib/qt3/lib/

same.

checking for Qt... configure: error: Qt (>= Qt 2.2.2) (libraries) not found. Please check your installation!

any help please!?

running mandrake 10.1
bones996
03-10-2005, 03:20 AM
Try the following instead of --with-qt-libraries
" ./configure --with-qt-dir=/usr/lib/qt3.3"
This way the program finds the directory (and headers) by itself most of the time. You will also have to have qt-devel installed to be able to install some programs from source - which may be the problem (libraries & headers are usually found in the devel packages).
h4n9m4n
03-10-2005, 08:56 PM
i used "./configure --with-qt-dir=/usr/lib/qt3" and
nope, no luck. thanks anyways. when i do that, i get the same error. when i do urpmi qt3, i get

[root@localhost komba2-0.7.3]# urpmi qt3
The following packages contain qt3:
libqt3
libqt3-devel
libqt3-mysql
libqt3-odbc
libqt3-pch-headers
libqt3-psql
qt3-common
qt3-example

so thats not a problem...
what's wrong?
cybertron
03-10-2005, 10:49 PM
Originally posted by h4n9m4n
i check the config.log and i find this

/usr/bin/ld: cannot find -lqt

That's because Mandrake compiles QT multi-threaded, so it needs -lqt-mt. I've never run into that problem before in a configure script since they're supposed to auto-detect things like that, so unfortunately I'm not sure what you can do. It might give you something to look for though.

Out of curiousity, what program is still looking for QT 2 libraries? That could very well be part of the problem since that is a very old version. They've been up to version 3 for at least a couple of years now. Again, that probably doesn't help, but maybe someone knows of a way to fix it.:confused: