[Bug 191991] www/chromium fails configure steps

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191991

--- Comment #2 from Stephen Hurd <shurd at FreeBSD.org> ---
I can confirm that my Python2.7 on 10.0-RELEASE-p7 appears to not support
queues:

root at portable:/usr/ports/www/chromium # python
Python 2.7.8 (default, Jul 18 2014, 02:59:47) 
[GCC 4.2.1 Compatible FreeBSD Clang 3.3 (tags/RELEASE_33/final 183502)] on
freebsd10
Type "help", "copyright", "credits" or "license" for more information.
>>> import multiprocessing
>>> from multiprocessing import queues
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/multiprocessing/queues.py", line 48, in
<module>
    from multiprocessing.synchronize import Lock, BoundedSemaphore, Semaphore,
Condition
  File "/usr/local/lib/python2.7/multiprocessing/synchronize.py", line 59, in
<module>
    " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation,
therefore, the required synchronization primitives needed will not function,
see issue 3770.

Adding the promising-looking --no-parallel to the gyp command-line does not
seem to help though.  Nor does adding no_parallel=1 or parallel=0 to the
defines.

Python 3.3.5 on the same system does seem to have working queues though:

root at portable:/usr/ports/www/chromium # python3
Python 3.3.5 (default, Apr 20 2014, 15:47:23) 
[GCC 4.2.1 Compatible FreeBSD Clang 3.3 (tags/RELEASE_33/final 183502)] on
freebsd10
Type "help", "copyright", "credits" or "license" for more information.
>>> import multiprocessing
>>> from multiprocessing import queues
>>> 

But I apparently can't use it to run gyp:

root at portable:/usr/ports/www/chromium # setenv PYTHON_VERSION python3.3
root at portable:/usr/ports/www/chromium # make configure
===>  chromium-35.0.1916.153_1 needs Python 2.7 at most. But you specified 3.3.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium

While building python 2.7 with the (non-default) PTH option looks like it would
work, that seems unsatisfactory as a requirement to build Chromium.

-- 
You are receiving this mail because:
You are on the CC list for the bug.