[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FTBFS: python



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Santiago Vila <sanvila@unex.es> writes:

> 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.
> make[1]: *** [sharedmods] Error 134
> make[1]: Leaving directory `/build/buildd/python2.3-2.3.2/build-static'
> make: *** [stamp-build-static] Error 2

I was trying to build it as well, as i would like to build some of my packages for Hurd.
I had to set the LD_LIBRARY_PATH, i still don't know why it is needed, and then got the
same problem.

> My build environment is packages from ftp.debian.org + old X packages
> from alpha.gnu.org. python2.2 has similar problems. Build logs here:
>
> http://people.debian.org/~sanvila/ftbfs/python2.2.build
> http://people.debian.org/~sanvila/ftbfs/python2.3.build

As my Hurd box crashed, my environment now use ftp.gnuab.org, ftp.us.debian.org and
www.htu.tugraz.at packages; only perl packages were taken from an old environment as
there were not available.

Are you OK to work in cooperation ?

Thx

Duck
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQE/uMBosczZcpAmcIYRAgGAAJwM0EZlSv/XyfJpIkZKyHNmyRwtHQCgmiOz
EP1K78QbfYMVYZ96EnXquNw=
=3HuY
-----END PGP SIGNATURE-----



Reply to: