Defining the Qt libraries in the ./configure

[Wallex]

checking for Qt... configure: error: Qt (>= Qt 3.0.3) (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!

1. I did compile and installed Qt with thread support (how could I not remember the six hours it took to make and make install it?
2. I have Qt 2.3.2 and 3.0.3 installed. Rpm -ql qt3 gives me the following results:
/etc/X11/qtrc
/usr/bin/qtconfig
/usr/lib/libqt-mt.so.3
/usr/lib/qt-3.0.3
/usr/lib/qt-3.0.3/bin
/usr/lib/qt-3.0.3/bin/qtconfig
/usr/lib/qt-3.0.3/etc
/usr/lib/qt-3.0.3/etc/settings
/usr/lib/qt-3.0.3/etc/settings/qtrc
/usr/lib/qt-3.0.3/lib
/usr/lib/qt-3.0.3/lib/libqt-mt.so.3
/usr/lib/qt-3.0.3/lib/libqt-mt.so.3.0
/usr/lib/qt-3.0.3/lib/libqt-mt.so.3.0.3
/usr/lib/qt-3.0.3/plugins
/usr/lib/qt-3.0.3/plugins/imageformats
/usr/lib/qt-3.0.3/plugins/imageformats/libqjpeg.so
/usr/lib/qt-3.0.3/plugins/imageformats/libqmng.so
/usr/lib/qt3
3. ./configure --help tells me:
--with-qt-libraries=DIR where the Qt library is installed.
4. So.. following my logic, I tried with these commands:
./configure --with-qt-libraries=/usr/lib/qt-3.0.3/lib
./configure --with-qt-libraries=/usr/lib/libqt-mt.so.3
./configure --with-qt-libraries=/usr/lib/qt-3.0.3
./configure --with-qt-libraries=/usr/lib/qt3

NONE of these worked, it still tells me qt3.0.3 is not installed. What am I doing wrong?

[Infrastructure]

You could try to run ldconfig.

For more info:

man ldconfig

[Wallex]

I ran ldconfig, lots of stuff happened, but it still says I have qt2.3.2. How do I know if the ldconfig did what I wanted? Because I am not even sure what I am supposed to bind (I know I should tell qt to use the libraries in /usr/lib/qt3)... the man gives me the 'syntax', but I am not so sure what this syntax means:
/sbin/ldconfig [ -nNvXV ] [ -f conf ] [
-C cache ] [ -r root ] directory ...
/sbin/ldconfig -l [ -v ] library ...
/sbin/ldconfig -p

Do I invoke the ldconfig three times?
Since this is something I have to do as root, I want to make sure I am not going to screw up. What I am thinking is maybe doing a
/sbin/ldconfig -lv /usr/local/qt /usr/lib/qt3 ?
This puzzles me... was I supposed to just run ldconfig -v and let it work? Because I did that and no change. I guess the problem here is not ldconfig but me, because I am not sure what exactly is the library and what I have to bind it to. I am certain I have to bind Qt with the Qt3 lib, but I only know the dirs where these are stored... um... I am puzzled. Anyone can enlighten me on the issue?

[mdwatts]

You could set your default QT directory in /usr/bin/startkde

export QTDIR=/usr/lib/qt3

That is where mine is defined.

[Infrastructure]

I also found these links, hope they can help you:

http://doc.trolltech.com/3.0/install-x11.html

http://www.trolltech.com/developer/platforms/linux.html

[X_console]

Does /etc/ld.so.conf contain the directory to your Qt library? If not, backup /etc/ld.so.conf and /etc/ld.so.cache, add the path to the Qt library directory to /etc/ld.so.conf, and run ldconfig again. See if that helps.

[windoze killa]

Try seting you qt lib to /usr/lib/qt-3.0.3 instead of /usr/lib/qt3 and see what happens. It seems that that was the output of the rpm -q that you ran.

[Wallex]

Guess what? I did what the 'installation guide of Qt' told me to do. When I first installed Qt3 I also followed the instructions, but I was forced to remove the Qt lines from my .profile file because those lines seemed to mess up my KDE+Glow enviroment. The glow buttons would just not work anymore and I got a crash everytime I closed a program. Well... I do not have to worry about that anymore because I am not using KDE anymore! Since I am now in Fluxbox I don't have to worry about that... altough it is strange that it started to crash, because, KDE3.0 should require Qt3.0.3 to start with, no? Oh well, at least it's fixed... somehow, it is fixed. Thanks for all the help.

And Killa, Qt3 and Qt2 are symlinks to qt3.0.3 and to qt2.3.2 respectively, so that wouldn't make much of a change. Suse has a strange way of manipulating files... it uses a lot the /opt dir. (startkde was in /opt/kde3/bin)