Mark,

I know when you install qt from source you have to set up the
QT_LIBRARY_PATH and point it to the place where QT is installed.

I'm not %100 sure that it is called QT_LIBRARY_PATH, it could be QT_PATH
or something similiar, download the source and check the
REAME or INSTALL file they explain this path and also give a peice of
code you can cut & paste into your /etc/profile file if
you wish to do so.

rpm finds it, because rpm keeps track of all files insatll though rpm. 
The other program doesn't find it because it is looking
for a QT_LIB_PATh (or something simlair) and isn't finding it, since it
might not exist yet.

Do you have a library path?, you may wish to include the path to QT
there first and see if that works, the try adding QT_PATH 
(or something simlair).  Check the README and INSTALL files that come
with the QT libraries.

Standard Disclamier.

It has been more than a year since I have used QT and KDE, which in the
software, esp OSS world, alot can change in a year or more.  

Jack


Mark Aitken wrote:
> 
> Hello,
> 
> I have tried now several times to install software,  RPMS, that tell me that QT libs 
>are not found when I do a './configure'.

I don't understand, RPM don't use a configure command, I ussually think
of "install by source(TM)" when I see commands like
./configure and make.  Configure will probably tell you they are not
installed, sure it has that fearture.

> 
> The main package in question is KPACKAGE RPM Manager.

Never heard of it, I take it is a KDE package for RPM managment? 


> So like any good boy I went to the CD and found qt-1.4-1.i386.rpm and did a 'rpm -i 
>qt-1.4-1.i386.rpm' only to be told
> 
> 'error:package qt-1.44-6 (which is newer then qt-1.4-1) is already installed'

Sure, your disturbation probably preinstalled it for you.

> 
> So why does my Kpackage install (./configure) report that it can not find QT????  I 
>am logged in as root.

See top of message.

btw, you shouldn't have to be logged in as root when config-ing a
program or making it, the only time you need to su to root is to do a
"make install" everything else can and should be done as a normal user. 
(%99 of the program I have build anyways).

> 
> bye for now

See Ya

> 
> MArk

JAck

Reply via email to