On Sun, Apr 25, 2004 at 05:05:32PM +0200, Matthias Klose wrote:
> Michael Banck writes:
> > > It seems that the pthread init hook is not being run by libc during
> > > start up. Try adding -lpthread and see if that makes a difference.
> >
> > That indeed helps. On the other hand, generally adding -lpthread to
> > $LDFLAGS makes linking libpython fail. I've built _tkinter.so manually
> > and assembled a hacked python2.3 package which I've uploaded to
> > ftp.gnuab.org:
> >
> > http://ftp.gnuab.org/debian/pool/main/p/python2.3/python2.3_2.3.3-6.0.1.changes
>
> In setup.y, add after "# Add the Tcl/Tk libraries"
>
> if platform == '<hurd platform name>':
> libs.append('pthread')
Well,
if platform == 'gnu0':
libd.append('pthread')
really adds -lpthread to the command line. Unfortunately, this does not
help as the error still remains:
gcc -shared build/temp.gnu-0.3-i386-AT386-2.3/_tkinter.o
build/temp.gnu-0.3-i386-AT386-2.3/tkappinit.o -L/usr/X11R6/lib
-lBLT -ltk8.4 -ltcl8.4 -lX11 -o
build/lib.gnu-0.3-i386-AT386-2.3/_tkinter.so
python: ../../libpthread/sysdeps/generic/pt-mutex-timedlock.c:55:
__pthread_mutex_timedlock_internal: Assertion
`__pthread_threads' failed.
make[1]: *** [sharedmods] Error 134
make[1]: Leaving directory `/build/buildd/python2.3-2.3.2/build-static'
make: *** [stamp-build-static] Error 2
Running the above command-line by hand makes _tkinter.so build fine (and
results in an identical binary as generated by setup.py prior to the
failure), the error must be from a different, invisible call from
distutils perhaps? Is there some way to make it more verbose?
Michael
--
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mbanck/diary.html
