Your system is KDE1 - of course it has no problem with KDE2 libraries being
the default !
upgrade man, upgrade - wake up and smell the 00's bro :-)
Oded
--
The point of philosophy is to start with something so simple as not to seem
worth
stating, and to end with something so paradoxical that no one will believe
it.
-- Bertrand Russell, The Philosophy of Logical Atomism
----- Original Message -----
From: "Alex Dubrovsky" <[EMAIL PROTECTED]>
To: "Oded Arbel" <[EMAIL PROTECTED]>
Cc: "Linux-IL mailing list" <[EMAIL PROTECTED]>
Sent: Sunday, January 28, 2001 09:19
Subject: Re: problems compiling kde1 applications
> Hi there.
> I don't know about other solutions posted , but on my rh6.2 system the
> solution was as simple as altering the QTDIR system variable - it was
pointing
> by default at the qt2 lib dir and the configure script took it from there.
> my 2c
> Oded Arbel wrote:
>
> > Hi list !
> >
> > I have a problem compiling KDE 1 applications, and since I think this
one is
> > quite common on the distro I use (Mandrake 7.2) I would gather that many
had
> > encountered this problem , so I'd like to hear input , if you please :
> >
> > When trying to ./configure an application for KDE 1 (as most KDE
> > applications are today - including kdevelop), I get a report about
problems
> > compiling a small KDE application (the headers are to blame) and then
(if I
> > pass that one) a problem with linking the application (this time the
> > libraries are to blame).
> > I do have both kde1-compat RPMs installed, but they way I see it is this
:
> > with the --prefix=/usr (as it should be for this system - nothing goes
into
> > /opt here), ./configure (dumbly) prefer to use the headers from
/usr/include
> > and the libraries from /usr/lib (where KDE2 and QT2 headers and
libraries
> > sit) rather then the ones from the /usr/lib/kde1-compat and /usr/lib/qt
> > directories - even if I explicitly specify to use the headers and
libraries
> > from the correct dirs (using --with-qt and --with-kde . note on that in
a
> > sec)!
> > the configure script also does not recognize the --with-kde options
though
> > it does recognize the --with-qt ones.
> > I know I can hack the configure script easily, but since I mostly want
to
> > compile source RPMs, I think this is a bad solution (since it will
require
> > me to path the sources after "installing" the RPM and before building
t -
> > for every package I install).
> > I can also specify --prefix=/usr/lib/kde1-compat
> > and --with-qt-dir=/usr/lib/qt in the spec file (which is easier then
> > patching the sources, but still not really desired), but I feel this is
bad
> > too (correct me if I'm wrong, but that would cause the resulting
binaries to
> > be installed under /usr/lib/kde1-compat/bin , right ?)
> >
> > So - basically I was wandering if mayhap anyone out there has a magic
> > solution :-)
> >
> > TIA
> >
> > Oded
> >
> > --
> > Pacey: "Isn't she beautiful ?"
> > Joey: "Yes, in a Titanic post-iceberg sort of way"
> > -- Dawson's Creek
> >
> > =================================================================
> > To unsubscribe, send mail to [EMAIL PROTECTED] with
> > the word "unsubscribe" in the message body, e.g., run the command
> > echo unsubscribe | mail [EMAIL PROTECTED]
>
>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
