Thomas Reitelbach wrote: > On Wednesday 08 January 2003 18:33, Roman Stepanov wrote: > > Jon Keating wrote: > > > On Wednesday 08 January 2003 06:19 am, Roman Stepanov wrote: > > > > After new stable release of Licq has been announced I decided to > > > > upgrade from licq-20021111 to a licq-20030108 snapshot. I've built a > > > > new package, installed it and finally got a segfault: > > Ouch, this looks like Licq is using two different QT libs at the same time! > Please make sure that Licq always finds _one_ QT lib, here it finds > libqt.so.1 AND libqt.so.2 which may be the reason for your problems.
Thanks a lot! The problem is that SuSE 7.3 has libqt* symlinks ln /usr/lib pointing to the actual locations of the libraries. If you have both QT1 and QT2 installed you have the following symlinks in /usr/lib: /usr/lib/libqt.so -> libqt.so.1.45 /usr/lib/libqt.so.1-> libqt.so.1.45 /usr/lib/libqt.so.1.45 -> qt/lib/libqt.so.1.45 /usr/lib/libqt.so.2 -> qt2/lib/libqt.so.2 This can fool libtool in some situations and make it link kde-gui with both QT1 and QT2. I've found that I can work around this problem with passing LDFLAGS="-L/usr/lib/qt2/lib -L/usr/lib" to ./configure script. -- WBR, Roman http://www.svartalf.tk ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
