From owner-freebsd-python@FreeBSD.ORG Sun Sep 14 20:33:14 2008 Return-Path: Delivered-To: python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E1F81065672 for ; Sun, 14 Sep 2008 20:33:14 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2ACB28FC13 for ; Sun, 14 Sep 2008 20:33:14 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.2) with ESMTP id m8EKY3ki019731 for ; Sun, 14 Sep 2008 15:34:03 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id m8EKY3YR019730 for python@FreeBSD.org; Sun, 14 Sep 2008 15:34:03 -0500 (CDT) (envelope-from brooks) Date: Sun, 14 Sep 2008 15:34:03 -0500 From: Brooks Davis To: python@FreeBSD.org Message-ID: <20080914203403.GC69101@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M38YqGLZlgb6RLPS" Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Sun, 14 Sep 2008 15:34:03 -0500 (CDT) Cc: Subject: python 2.5 not linking with threads on 7.0 i386? X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2008 20:33:14 -0000 --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--