freebsd-ports/lang/python34
Kubilay Kocak c0cd7bc6cc lang/python34: Fix build when semaphores are not enabled
Backport fix [1] for upstream Python Issue #21704 [2]: Fix build error for
_multiprocessing when semaphores are not available.

The symptom was originally reported by RedPorts 8.4-QAT/i386,
ultimately resulting in a packaging error:

  ...
  checking for sem_open... yes
  checking for sem_timedwait... yes
  checking for sem_getvalue... yes
  checking for sem_unlink... yes
  ...
  checking whether POSIX semaphores are enabled... no
  checking for broken sem_getvalue... yes
  ...

  *** WARNING: renaming "_multiprocessing" since importing it failed:
  build/lib.freebsd-8.4-RELEASE-i386-3.4/_multiprocessing.so: Undefined
  symbol "_PyMp_sem_unlink"

  ...

  pkg-static: lstat(/work/a/ports/lang/python34/work/stage/usr/local/lib/
  python3.4/lib-dynload/_multiprocessing.so): No such file or directory

Something is funny for Jail-based systems when it comes to host/jail
semaphore detection. A config.log would be handy to help determine why.

[1] http://hg.python.org/cpython/rev/f618f6739200
[2] http://bugs.python.org/issue21704
2014-08-25 07:59:45 +00:00
..
files lang/python34: Fix build when semaphores are not enabled 2014-08-25 07:59:45 +00:00
distinfo Update python34 port 3.4.0 --> 3.4.1. 2014-06-02 12:36:51 +00:00
Makefile lang/python34: Fix build when semaphores are not enabled 2014-08-25 07:59:45 +00:00
pkg-descr
pkg-plist - Remove everything related to USE_PYTHON and bsd.python.mk. This is a 2014-08-01 15:52:42 +00:00