That *IS* one annoying aspect to RPM and Tarball build methods. I
usually have to add --prefix=/usr to the ./configure command to keep the
binaries in /usr/bin instead of /usr/local/bin. Perhaps something
similar can be done with QT.
Peter Ruskin wrote:
>
> On Monday 18 June 2001 20:27, Paul Cox wrote:
> > On Monday, Jun 18, 2001, Peter Ruskin wrote:
> > > > Thanks, Paul. I did a --rebuild on the kdelibs.src (What a grind!--
> [���]
> > > I tried that - unsuccessfully. At the configure stage I got this
> > > message: checking for Qt... configure: error: Qt (>= Qt 2.2.2)
> > > (libraries) not found.
> > >
> > > After no end of symlinking and ldconfigging - still this message. If I
> > > go into the /usr/src/RPM/BUILD/kdelibs-2.1.2 directory and do
> > > `./configure --with-qt-dir=/usr/local/qt-2.3.1` it works fine. Then I
> > > make && make install and KDE is OK - but of course the RPM database
> > > isn't.
> >
> > Mmm... your qt-dir is in /usr/local? Did you not use the 8.0 .rpms for qt?
>
> Yes, but I installed qt-2.3.1 from source - that usually goes in
> /usr/local/qt (symlinked to /usr/local/qt-2.3.1 in my case). QTDIR is set in
> /etc/profile to /usr/local/qt.
>
> To try to rebuild kdelibs-2.1.2 I disabled qt-2.3.1 and set QTDIR to
> /usr/lib/qt2 (where the 8.0 version lives) but that didn't work either.
> --
> Peter Ruskin, Wrexham, Wales.
> Registered Linux User No. 219434 ( see http://counter.li.org/ )
> Linux Mandrake release 8.0 (Traktopel) for i586
> Linux 2.4.3-20mdk-win4lin-pnr, KDE: 2.1.2, Qt: 2.3.1
> Uptime 3 days 5 hours 30 minutes
