Date: Sun, 14 Sep 2008 15:34:03 -0500 From: Brooks Davis <brooks@FreeBSD.org> To: python@FreeBSD.org Subject: python 2.5 not linking with threads on 7.0 i386? Message-ID: <20080914203403.GC69101@lor.one-eyed-alien.net>
next in thread | raw e-mail | index | archive | help
--M38YqGLZlgb6RLPS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It looks like the python 2.5 port is failing to actually link with a threading library on 7.0 i386. I was having issues with psycopg2 causing python to hang in state ucond when loaded on one machine and after a bunch of investigation discovered that while python was set to link with threads, ldd on python didn't show a threading library: /usr/local/bin/python: libutil.so.7 => /lib/libutil.so.7 (0x28157000) libm.so.5 => /lib/libm.so.5 (0x28164000) libc.so.7 => /lib/libc.so.7 (0x28179000) I replicated this on another i386 machine, but only after discovering this isn't the case on a couple amd64 machines: /usr/local/bin/python: libutil.so.7 => /lib/libutil.so.7 (0x80070e000) libm.so.5 => /lib/libm.so.5 (0x80081d000) libthr.so.3 => /lib/libthr.so.3 (0x800937000) libc.so.7 => /lib/libc.so.7 (0x800a4d000) Adjusting the postgres config the not link against libthr (via libintl) seems to have fixed the problem I was seeing which leads me to belive this really is a threading support issue. -- Brooks --M38YqGLZlgb6RLPS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIzXU6XY6L6fI4GtQRAt9OAJ9JJkzlmLsnVrndN0R72fls/exYaQCeNyUR hfLzpA5fvLEi2m4BxIiMJ0E= =WSfr -----END PGP SIGNATURE----- --M38YqGLZlgb6RLPS--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080914203403.GC69101>