Hi List! It seems that linking against qt-mt is not the fault...
I temporarely removed my libqt-mt.so to force the configure-script to use libqt.so. But the result is similar... ~> licq -p kde-gui Licq Segmentation Violation Detected. Backtrace: licq(licq_handle_sigsegv+0x7b) [0x809ef5b] /lib/libpthread.so.0(pthread_kill+0x174) [0x40129bc4] /lib/libc.so.6(__libc_sigaction+0x138) [0x401ea7f8] /usr/X11R6/lib/X11/locale/common/ximcp.so.2(_XimCheckIfLocalProcessing+0x59) [0x41dd5e4d] /usr/X11R6/lib/X11/locale/common/ximcp.so.2(_XimOpenIM+0x256) [0x41dd57d2] /usr/X11R6/lib/libX11.so.6(_XlcDynamicLoad+0x1bb) [0x406fa06b] /usr/X11R6/lib/X11/locale/common/ximcp.so.2(_XimRegisterIMInstantiateCallback+0xc9) [0x41dd4e9d] /usr/X11R6/lib/libX11.so.6(_XlcDynamicLoad+0x2cb) [0x406fa17b] /usr/X11R6/lib/libX11.so.6(XRegisterIMInstantiateCallback+0x48) [0x406dc774] /usr/lib/qt3/lib/libqt.so.3(qt_init_internal__FPiPPcP9_XDisplayUlUl+0x1c87) [0x408c6247] /usr/lib/qt3/lib/libqt.so.3(qt_init__FPiPPcQ212QApplication4Type+0x29) [0x408c7029] /usr/lib/qt3/lib/libqt.so.3(construct__12QApplicationRiPPcQ212QApplication4Type+0x68) [0x40918ce8] /usr/lib/qt3/lib/libqt.so.3(__12QApplicationRiPPcb+0x61) [0x40918b81] /opt/kde3/lib/libkdecore.so.4(__12KApplicationRiPPcRC8QCStringbT4+0x2e) [0x4104305e] /opt/licq/lib/licq/licq_kde-gui.so(__8CLicqGuiiPPc+0x4c) [0x4033ca2c] /opt/licq/lib/licq/licq_kde-gui.so(LP_Main+0x45) [0x4033c2a5] /opt/licq/lib/licq/licq_kde-gui.so(LP_Main_tep+0x22) [0x4033bf82] /lib/libpthread.so.0(pthread_detach+0x597) [0x40126f37] /lib/libc.so.6(__clone+0x3a) [0x40293b1a] Attempting to generate core file. Real-Time Signal 1 Hope I could help... Greets, Daniel _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
