Re: [Cooker] cooker and licq
"Lord And Master;)" wrote: I have noticed that cooker is still using licq version 75.3a version 80.0 is out and has many many new features, and they have aslo fixed the yes it is out. i am waiting for the neew gtk + licq (currently the old one doe not compile with 0.80 but i have hacked the code so that it compiles.) when the official gtklicq comes out i will update the src rpm and send it to lenny. spec file so it compiles correctly now (with out munkieing with the configure scripts.) we need qt 2.1 and 80 in cooker, it is very stable and has multi person chat as well as a lot of other features. -DarkWlf -- #!/bin/sh cat EOF Regards, snail talk (geoff), master linux system administrator ;-) EOF
Re: [Cooker] cooker and licq
Chmouel Boudjnah wrote: "Lord And Master;)" [EMAIL PROTECTED] writes: what problems maybe I can help? the /usr/lib/libqt.so stuff, configure of licq search (via nm) the symbols of qt2 but /usr/lib/libqt.so come from qt1.4 by default on mandrake (this should be a AUTOMAKE fix). but i never had any problems..it's working great for me... -- MandrakeSoft Inchttp://www.mandrakesoft.com In Travel --Chmouel -- #!/bin/sh cat EOF Regards, snail talk (geoff), master linux system administrator ;-) EOF
Re: [Cooker] cooker and licq
"Sergio P. Korlowsky" wrote: "Lord And Master;)" wrote: I have noticed that cooker is still using licq version 75.3a version 80.0 is out and has many many new features, and they have aslo fixed the spec file so it compiles correctly now (with out munkieing with the configure scripts.) we need qt 2.1 and 80 in cooker, it is very stable and has multi person chat as well as a lot of other features. -DarkWlf I noticed licq latest releases uses qt-2.02 I can find 2.1x but were is qt-2.02? Thnaks for the info... I am still using licq that came with mdk-7.02 Serge .80 dose not use 2.0.2 anymore at all and now requires 2.1 it states right on the licq webpage. -DarkWlf
Re: [Cooker] cooker and licq
geoffrey lee wrote: Chmouel Boudjnah wrote: "Lord And Master;)" [EMAIL PROTECTED] writes: what problems maybe I can help? the /usr/lib/libqt.so stuff, configure of licq search (via nm) the symbols of qt2 but /usr/lib/libqt.so come from qt1.4 by default on mandrake (this should be a AUTOMAKE fix). but i never had any problems..it's working great for me... -- MandrakeSoft Inchttp://www.mandrakesoft.com In Travel --Chmouel -- #!/bin/sh cat EOF Regards, snail talk (geoff), master linux system administrator ;-) EOF the problem is that the checks for qt look for libqt.so and not libqt.2.so so it will fail if there in the same dir, you have to have the qt in a seperate dir with a ln to the qt2 libs etc. for the configure and automake scripts in licq to work. -DarkWlf
RE: [Cooker] cooker and licq
hi, the problem is that the checks for qt look for libqt.so and not libqt.2.so so it will fail if there in the same dir, you have to have the qt in a seperate dir with a ln to the qt2 libs etc. for the configure and automake scripts in licq to work. i have got licq 0.80 to build on my system with no problems. i just needed to make one patch (for configure.) i got it to build with qt 2.0.x, no problems. i have proof of this, because i'm using it on my systm right now. anyone looking for the 0.80 binary package? ;-) geoff. -DarkWlf
Re: [Cooker] cooker and licq
geoffrey lee wrote: hi, the problem is that the checks for qt look for libqt.so and not libqt.2.so so it will fail if there in the same dir, you have to have the qt in a seperate dir with a ln to the qt2 libs etc. for the configure and automake scripts in licq to work. i have got licq 0.80 to build on my system with no problems. i just needed to make one patch (for configure.) i got it to build with qt 2.0.x, no problems. i have proof of this, because i'm using it on my systm right now. anyone looking for the 0.80 binary package? ;-) geoff. -DarkWlf I am using it here as well, I had not checked the bug with configure yet in that version as I'm now using the qt2.1 libs -DarkWlf
RE: [Cooker] cooker and licq
yo! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, March 24, 2000 11:52 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] cooker and licq geoffrey lee wrote: hi, the problem is that the checks for qt look for libqt.so and not libqt.2.so so it will fail if there in the same dir, you have to have the qt in a seperate dir with a ln to the qt2 libs etc. for the configure and automake scripts in licq to work. i have got licq 0.80 to build on my system with no problems. i just needed to make one patch (for configure.) i got it to build with qt 2.0.x, no problems. i have proof of this, because i'm using it on my systm right now. anyone looking for the 0.80 binary package? ;-) geoff. -DarkWlf I am using it here as well, I had not checked the bug with configure yet in that version as I'm now using the qt2.1 libs ok. not sure about 2.1, because it's still devel and i don't use that. i guess a fix would be to patch configure so that it checks for /usr/lib/libqt.so.2 (it is a symlink.) that way we will alwyas be compiling with qt2. it would be the quickest and most painless fix, since, if i remember correclty, it only involvdes changing one line. i can't remember what i did to configure last time. i think i got it to check libqt.so.2.0.2 .. geoff. -DarkWlf
RE: [Cooker] cooker and licq
hi, *nods* I have been through this fix , with the configure.. it is two lines actualy, i just put a * at the end of each checks so it checks all the files libqt.* ok. this fix is acceptable since only qt2 has QCString. i will change the patch on my own system. that worked well but i still feel the the qt2 should be in it's own directory makes things simpler as you can simply pass the qt dir something inherited from redhat i guess ;-) , where you shove every non-critical library into /usr/lib to the configure and it will then find the libs the includes and the correct moc files with out hasleing with modifing the configure scripts it's not a big problem as far as licq is concerned since this is only one line of patch. not sure about building other qt2 applications, jeez, i hardly ever use them anyway. geoff. 80 fyi finds /usr/lib/qt2.1/ files correctly without any modification. -DarkWlf
Re: [Cooker] cooker and licq
Chmouel Boudjnah wrote: "Lord And Master;)" [EMAIL PROTECTED] writes: I have noticed that cooker is still using licq version 75.3a version 80.0 is out and has many many new features, and they have aslo fixed the spec file so it compiles correctly now (with out munkieing with the configure scripts.) we need qt 2.1 and 80 in cooker, it is very stable and has multi person chat as well as a lot of other features. it will be the last version we still have some problems which need to be fixed. -- MandrakeSoft Inchttp://www.mandrakesoft.com In Travel --Chmouel what problems maybe I can help? -darkwlf
Re: [Cooker] cooker and licq
On Thu, Mar 23, 2000 at 12:28:07PM -0600, Lord And Master;) wrote: Chmouel Boudjnah wrote: "Lord And Master;)" [EMAIL PROTECTED] writes: what problems maybe I can help? the /usr/lib/libqt.so stuff, configure of licq search (via nm) the symbols of qt2 but /usr/lib/libqt.so come from qt1.4 by default on mandrake (this should be a AUTOMAKE fix). -- MandrakeSoft Inchttp://www.mandrakesoft.com In Travel --Chmouel with the qt2.1 libs i'm using from contrib (updated to beta 2 version though) everything is placed in /usr/lib/qt2.1/* and that works quite well because it auto maticly finds them in the latest version's of licq. no automake required just ./configure and done. I have gone round and round with the author with the /lib/libqt stuff and he has refused to change it to search for libqt.2 so I simply placed everything in /usr/lib/qt2.1 and tell it qt base is in /usr/lib/qt2.1 (although with 80 you don't have to do that either) and everything works flawlessly. no mess no fuss:) unless we plan on getting rid of qt 1.4 i don't see this problem going away to easily with haveing the files in the same dir. I'm updating qt2.1 to beta3 (for koffice). Should I use /usr/lib/qt2.1 then ? Do you really mean /usr/lib/qt2.1/libqt.so.2.1.0 ? Sounds like a very good idea, since /usr/lib/libqt.so.2 is already used for 2.0 -- David FAURE [EMAIL PROTECTED], [EMAIL PROTECTED] http://home.clara.net/faure/ KDE, Making The Future of Computing Available Today
