Sean Townsend wrote: > > Thanks guys. The thing is though, is that I have the latest QT libraries > installed. I can't figure out why the installation is not finding them. I'm > running KDE 2.0.1, I had to upgrade the QT libraries at that time to get KDE 2 > to install. Also, I get the same error whether I rpm it or install it from > source. > > "Andrew A. Chen" wrote: > > > > > checking for Qt... configure: error: Qt (>= 2.0) (libraries) not found. > > > > Please check your installation! > > > > Bad exit status from /var/tmp/rpm-tmp.85756 (%prep) > > > > > > It means it can't find the qt libs revision 2.0 or higher. Usually they > > >are in /usr/lib/qt2 or that is a link to them. If your only running kde1 > > >then you probably only have a qt revision 1.x. There is an option to > > >.configure to tell it you have qt1.x/kde1.x. Go into the source dir > > >that rpm created for you and read the README/INSTAll file/files and > > >do a ./configure --help | more. Damn that was a long one. > > > > FYI, Slackware doesn't use RPMs by default, although 7.1 does include an > > rpm to pkg converter tool. For slackware, check /usr/doc and (if you have > > it) /usr/local/doc. It's really just easier to upgrade QT (./configure; > > sudo make all check install). Cheers > > Did you run ./configure from within the source directory and define where qt was --with-extra-libs=DIR adds non standard library paths --with-qt-dir=DIR where the root of Qt is installed --with-qt-includes=DIR where the Qt includes are. --with-qt-libraries=DIR where the Qt library is installed. I had the same problem until defining ALL of these for my path to qt for configure. configure --help to see all. -- Mark Hounschell dmarkh@xxxxxxxxxx