[issue10062] Python 3.2 does not build on systems which do not have sem_timedwait

Antoine Pitrou added the comment: Patch committed in r85352, thanks. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue10062] Python 3.2 does not build on systems which do not have sem_timedwait

Akira Kitada added the comment: The patch does fix the build error. Thank you! -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10062] Python 3.2 does not build on systems which do not have sem_timedwait

Antoine Pitrou added the comment: What about this patch? Index: Python/thread_pthread.h === --- Python/thread_pthread.h (révision 85348) +++ Python/thread_pthread.h (copie de travail) @@ -64,7 +64,8 @@ /* Whether or not to

[issue10062] Python 3.2 does not build on systems which do not have sem_timedwait

Akira Kitada added the comment: It works fine with USE_SEMAPHORES commented out. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue10062] Python 3.2 does not build on systems which do not have sem_timedwait

Antoine Pitrou added the comment: What happens if you comment out "# define USE_SEMAPHORES" in Python/thread_pthread.h? -- nosy: +pitrou ___ Python tracker ___ ___

[issue10062] Python 3.2 does not build on systems which do not have sem_timedwait

New submission from Akira Kitada : Build fails on FreeBSD 4 due to the lack of sem_timedwait. """ gcc -pthread -Wl,--export-dynamic -o python Modules/python.o libpython3.2.a -lutil -lm libpython3.2.a(thread.o): In function `PyThread_acquire_lock_timed': /home/akitada/src/py3k/Python/threa