Re: FTBFS: python

[Santiago Vila <sanvila@unex.es>]

On Sun, 2 Nov 2003, 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.

So where would you add such thing, exactly?

The configure script for python has some options which seem to be
thread-related:

  --with(out)-threads[=DIRECTORY]
                          disable/enable thread support
  --with(out)-thread[=DIRECTORY]
                          deprecated; use --with(out)-threads
  --with-pth              use GNU pth threading libraries


Should debian/rules use any of them in the configure line?