On Wed, May 14, 2008 at 09:07:42PM -0500, Justin Conover wrote: > > # pwd > /etc/ld.so.conf.d > # cat teamspeak.conf > /opt/TeamSpeak2RC2/lib > # ldconfig > > 1# cd /opt/TeamSpeak2RC2/lib > > # ll > total 7772 > lrwxrwxrwx 1 root root 16 2008-05-14 21:01 HVDI.so.0.8 -> libHVDI.so.0.8.0 > lrwxrwxrwx 1 root root 21 2008-05-14 21:01 libborqt-6.9.0-qt2.3.so -> > libborqt-6.9-qt2.3.so > -rwxr-xr-x 1 root root 7526184 2008-05-14 21:00 libborqt-6.9-qt2.3.so > -rwxr-xr-x 1 root root 180344 2008-05-14 21:00 libHVDI.so.0.8.0 > lrwxrwxrwx 1 root root 17 2008-05-14 21:01 libspeex.so.1 -> > libspeex.so.1.0.0 > -rwxr-xr-x 1 root root 224296 2008-05-14 21:00 libspeex.so.1.0.0 > > $ /opt/TeamSpeak2RC2/TeamSpeak.bin > /opt/TeamSpeak2RC2/TeamSpeak.bin: symbol lookup error: /opt/TeamSpeak2RC2/ > TeamSpeak.bin: undefined symbol: initPAnsiStrings Does 'ldd /opt/TeamSpeak2RC2/TeamSpeak.bin' shows something as "not found"? > > # ldconfig -v |more > snip > /opt/TeamSpeak2RC2/lib: > libborqt-6.9.0-qt2.3.so -> libborqt-6.9-qt2.3.so > HVDI.so.0.8 -> libHVDI.so.0.8.0 > libspeex.so.1 -> libspeex.so.1.0.0 So you are saying that all libraries from /opt/TeamSpeak2RC2/lib are found and everything looks like it should. And if you make them available from /usr/lib too then this "undefined symbol: initPAnsiStrings" is truly gone? I was guessing from an earlier information that 'libborqt' resolves that. Weird! Load order? Wait a minute! You should have quite a newer version of libspeex on your system. As a matter of fact there was fairly recently a security update. This is what ChangeLog says: - Security update: Add mode checks to speex_packet_to_header() to protect applications using speex library and not having proper checks (CVE-2008-1686, #441239, https://trac.xiph.org/changeset/14701) If you clobbered a system copy with an old stuff from Borland then who knows what may happen? Michal -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
