Subject: Re: libtcl84.so.1 Undefined PLT symbol "pthread_*"
To: Marc Recht <firstname.lastname@example.org>
From: Luke Mewburn <lukem@NetBSD.org>
Date: 08/17/2004 15:47:30
Content-Type: text/plain; charset=us-ascii
On Mon, Aug 16, 2004 at 11:25:48PM +0200, Marc Recht wrote:
| >As far as I can see, we build python with no threads or with pth,
| >yet libtcl gets built against pthreads, and so I don't see how it could
| >ever work.
| >Ie. the trick is to get libtcl to not use pthreads - or to get everying
| >else to use it?
| Indeed. FWIW, with 2.0 slowly showing up on the horizon, I thought more=
| than once to switch all python versions to build with threads by defaul=
That would be very useful.
I've been told that my recent fixes to python's signal handling has
improved the stability of threads-using python packages such as bittorrent.
These fixes are in python23 and python23-pth since ~ 2004/06/14.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (NetBSD)
-----END PGP SIGNATURE-----