Click to See Complete Forum and Search --> : QT question


Janet
09-08-2001, 08:41 AM
I am running Mandrake 8.0 and have several progs asking for QT 2.2.2 .
After much searching I found a 2.2.2 (qt-x11-2.2.2.tar.gz) which wouldnt install (didnt like my Linux).

I have installed the following QTs but the progs still ask for QT2.2.2 .
Any suggestions welcome.

libqt2-2.3.1-3mdk.i586.rpm
libqt2-devel-2.3.1-3mdk.i586.rpm
qt2-static-libraries-2.3.1-3mdk.i586.rpm

cabu1966
09-08-2001, 03:00 PM
I don't know a thing about Mandrake but I looked at Mandrakes site and found this qt2-Xt-2.3.0-3mdk.i586.rpm at their ftp site. Might give it a try, get it at
Mandrake ftp site (ftp://carroll.cac.psu.edu/pub/linux/distributions/mandrake/8.0/i586/Mandrake/RPMS/)
I believe for most programs to work that require it you need to have the shared libs available. I assume the rpm does that for you? I looked back at my configure and it did it by default, I didn't have to --enable-shared.

[ 08 September 2001: Message edited by: cabu1966 ]

Malakin
09-08-2001, 05:31 PM
Mandrake 8 comes with QT 2.3.0

These are the files on the first CD:
libqt2-2.3.0-3mdk.i586.rpm libqt2-devel-2.3.0-3mdk.i586.rpm

If something seems to be asking for qt 2.2.2, install the devel rpm and see if it's still asking for something qt related.

If you're trying to compile a program and it's asking for 2.2.2, override it's qt detection and it should work.

Janet
09-09-2001, 08:33 PM
Thanks Malakin,
The problem must be this overide as All the QT files are installed and it still want s QT2.2.2 could you be a little more specific on "override it's qt detection" .
Please dont misunderstand Im not lazy but I really wouldnt know where to start on this one.
Thanks

Malakin
09-09-2001, 09:32 PM
Actually I have a few more ideas:
Edit this file "/etc/ld.so.conf"
and put an entry for "/usr/lib/qt2/lib" in there, then type "ldconfig", try to run configure on the program again.

If it doesn't work try this:

Type "QTDIR=/usr/lib/qt2" then "./configure --with-qt-dir=/usr/lib/qt2"

If that still doesn't work then try this:

This last alternative isn't all that easy. But I'll usually type "grep "errormessage" configure -n" substituting part of the exact error message, this will tell me where in the configure script the error is coming from. I edit the configure script and just change the logic so instead of it going to an error if it can't find QT you just reverse it so if it can't find QT it continues.