On Sun, Jul 24, 2005 at 06:01:46PM -0600, Michael Fuhr wrote: > On Sun, Jul 24, 2005 at 06:40:35PM -0400, Tom Lane wrote: > > I think someone mentioned this already, but it'd be a good idea to > > compare the python situation to plperl. On my Linux box, libperl.so > > shows several references to pthread_xxx symbols ... not the same ones > > libpython.so depends on, but pthread symbols none the less. I'd kind > > of expect them both to fail if the problem is that the stock libc > > doesn't include pthreads. > > I have a FreeBSD 4.11-STABLE box with Perl 5.8.7 built from the > ports collection, and "nm libperl.so" shows no pthread functions. > The port's Makefile has a WITH_THREADS option that I don't think is > enabled by default. The Python port's Makefile, however, has a > WITHOUT_THREADS option, so I think it *does* build a threaded Python > by default.
FWIW, AFAICT I did build the port with default options. Though, nm shows no symbols for my libpython(s)... [EMAIL PROTECTED]:38]~:47>nm `locate libpython|grep .so` /usr/local/lib/compat/pkg/libpython2.3.so.1: /usr/libexec/elf/nm: /usr/local/lib/compat/pkg/libpython2.3.so.1: no symbols /usr/local/lib/libpython2.4.so: /usr/libexec/elf/nm: /usr/local/lib/libpython2.4.so: no symbols /usr/local/lib/libpython2.4.so.1: /usr/libexec/elf/nm: /usr/local/lib/libpython2.4.so.1: no symbols /usr/local/lib/python2.4/config/libpython2.4.so: /usr/libexec/elf/nm: /usr/local/lib/python2.4/config/libpython2.4.so: no symbols [EMAIL PROTECTED]:39]~:48> But I do have a /usr/local/lib/python2.4/config/libpython2.4.a that has a bunch of symbols, though I'm not sure if that means anything or what I'm looking for in the nm output. -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
