Re: FTBFS: python
On Sun, Nov 02, 2003 at 03:43:00PM -0500, Neal H. Walfield wrote:
> At Sun, 2 Nov 2003 19:53:31 +0100 (CET),
> Santiago Vila wrote:
> >
> > And this is what happens when compiling python2.3:
> >
> > gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC
> > -fno-strict-aliasing -DWITH_APPINIT=1 -DWITH_BLT=1
> > -I/usr/include/tcl8.4 -I/usr/X11R6/include -I.
> > -I/build/buildd/python2.3-2.3.2/./Include
> > -I/build/buildd/python2.3-2.3.2/Include
> > -I/build/buildd/python2.3-2.3.2/build-static -c
> > /build/buildd/python2.3-2.3.2/Modules/_tkinter.c -o
> > build/temp.gnu-0.3-i386-AT386-2.3/_tkinter.o 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.
>
> 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
I've CC'ed the python maintainers, perhaps they have an idea how to
handle this. Would be nice if people interested in python would test the
packages, they seem to work fine for me but I did not have the time to
install any other python packages/modules yet.
A couple of tests failed (namely, 'cpickle', 'parser', 'poll', 're' and
'socket'. 'class' did fail, too, but changing recursion_limit in
Python/ceval.c from 1000 to 930 made that pass on my machine at least)
with segfaults, which I removed (test-suite failures are not fatal to
the build, but the tests get byte-compiled during installation for
whatever reason and the segfaults happen there, too). I had a look at a
couple of them but when I was unable to figure out the third segfault in
a couple of hours I stopped there and gave up :-/
As the tests get removed in the package building later on anyway,
perhaps it can be avoided to byte-compile them at all?
enjoy,
Michael
--
Michael Banck
Debian Developer
mbanck@debian.org
http://www.advogato.org/person/mbanck/diary.html
Reply to: