Grab the qt2-devel and qt-2 rpm's from redhat 6.1!
rpm -ivh (not -Uvh, or you'll wipe out qt 1.44!, you don't want that)
when you ./configure the licq qt-gui do this
./configure --with-x --with-qt-includes=/usr/lib/qt-2.0.1/include/
--with-qt-libraries=/usr/lib/qt-2.0.1/lib/
That will get you going pretty quick and painless.
Rich Clark wrote:
> On Tue, 18 Jan 2000 [EMAIL PROTECTED] wrote:
>
> > Riyad Kalla wrote:
> >
> > > Its actually in the faq for licq... you are going to have to
> > > set your LD_LIBRARY_PATH to the directory with qt2.x in it, the only problem
> > > 1.x and 2.x are both in /usr/lib, so what I did was download qt2.x tar,
> > > compiled it myself and put it in its own dir /usr/local/lib/qt-2.0.2 and set
> > > my LD_LIBRARY_PATH to that dir, all the sudden LICQ ran fine. The problem
> > > you are getting is cause LICQ is finding 1.x versions of QT instead of 2.x
> > > hence the undefined symbols. So you have to contain 2.x by itself, I am sure
> > > there is mandrake way to do it, I just did it the easiest I could think of.
> > >
> > > Hope this helps
> >
> > Yeah, I figured that out after I poked around for a bit last night, and
> > installed qt the old fashioned way too, Thanks anyway though ;-)
> >
> >
> >
> > >
> >
> > --
> > [EMAIL PROTECTED]
> > ICQ 1796276
> >
> >
> >
> >
>
> I've grabbed the qt2 tarball from troll.no and I've run into a fustercluck
> of bugs in the code. I wish I knew more about C++ though; I'm guessing on
> what to do to fix this trash.
>
> --
> Rich Clark
>
> Sign the petition at http://www.libranet.com/petition.html
> Help bring us more Linux Drivers
--
[EMAIL PROTECTED]
ICQ 1796276
