On Thu, Nov 21, 2013 at 5:19 PM, james N. <ja...@flatlan.net> wrote:
> Hey list,
>
> I have a build issue with chromium on one machine but not the other.
> The version I'm trying to build is www-client/chromium-32.0.1700.19
> but the problem occurs on the current stable version also (31.0.1650.57).
>
>
>  * ERROR: www-client/chromium-32.0.1700.19::gentoo failed (configure phase):
>  *   (no error message)
>  *
>  * Call stack:
>  *     ebuild.sh, line  93:  Called src_configure
>  *   environment, line 4972:  Called die
>  * The specific snippet of code:
>  *       egyp_chromium ${myconf} || die
>  *
>  * If you need support, post the output of `emerge --info 
> '=www-client/chromium-32.0.1700.19::gentoo'`,
>  * the complete build log and the output of `emerge -pqv 
> '=www-client/chromium-32.0.1700.19::gentoo'`.
>  * The complete build log is located at
> '/var/tmp/portage/www-client/chromium-32.0.1700.19/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/www-client/chromium-32.0.1700.19/temp/environment'.
>  * Working directory: 
> '/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19'
>  * S: 
> '/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19'
>
>
> before that, the output is:
>
> Updating projects from gyp files...
> Traceback (most recent call last):
>   File "build/gyp_chromium", line 157, in <module>
>     sys.exit(gyp.main(args))
>   File
> "/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19/tools/gyp/pylib/gyp/__init__.py",
> line 527, in main
>     return gyp_main(args)
>   File
> "/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19/tools/gyp/pylib/gyp/__init__.py",
> line 503, in gyp_main
>     options.circular_check)
>   File
> "/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19/tools/gyp/pylib/gyp/__init__.py",
> line 129, in Load
>     params['parallel'], params['root_targets'])
>   File
> "/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19/tools/gyp/pylib/gyp/input.py",
> line 2687, in Load
>     generator_input_info)
>   File
> "/var/tmp/portage/www-client/chromium-32.0.1700.19/work/chromium-32.0.1700.19/tools/gyp/pylib/gyp/input.py",
> line 594, in LoadTargetBuildFilesParallel
>     parallel_state.pool = multiprocessing.Pool(8)
>   File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232, in Pool
>     return Pool(processes, initializer, initargs, maxtasksperchild)
>   File "/usr/lib64/python2.7/multiprocessing/pool.py", line 138, in __init__
>     self._setup_queues()
>   File "/usr/lib64/python2.7/multiprocessing/pool.py", line 232, in 
> _setup_queues
>     from .queues import SimpleQueue
>   File "/usr/lib64/python2.7/multiprocessing/queues.py", line 48, in <module>
>     from multiprocessing.synchronize import Lock, BoundedSemaphore, 
> Semaphore, Condition
>   File "/usr/lib64/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.
>
> Any ideas?
>
> Thanks
>
> --
> James
>
> This is my signature. Please don't steal it.
>

What kernel are you running and/or what kernel did you build python2.7
with?  I would try remerging dev-lang/python:2.7

Possibly relevant:
http://bugs.python.org/issue8326

-- 
Alecks Gates

Reply via email to