I've been bumping into failures installing Matplotlib 1.2.0-r2:
# cat /tmp/livecd-stage1.log
…
/build/lib/matplotlib/tests/baseline_images/test_delaunay
Traceback (most recent call last):
File "/usr/lib/python3.2/multiprocessing/synchronize.py", line 54, in
<module>
from _multiprocessing import SemLock
ImportError: cannot import name SemLock
…
ImportError: This platform lacks a functioning sem_open implementation,
therefore, the required synchronization primitives needed will not function,
see issue 3770.
…Looking through my logs, it seems that some versions of Python 3.2.3 found a sem_open implementation, but some did not: $ cd /var/log/catalyst $ grep sem_open dev-lang\:python-3.2.3\:* dev-lang:python-3.2.3:20130310-213508.log:checking for sem_open... yes dev-lang:python-3.2.3:20130310-222606.log:checking for sem_open... no dev-lang:python-3.2.3:20130310-234410.log:checking for sem_open... yes I cleaned out my logs before my last run, so we can match those build times up with stages: $ grep dev-lang/python-3.2.3 /tmp/*.log /tmp/stage1.log:>>> Emerging (14 of 17) dev-lang/python-3.2.3 /tmp/stage1.log:>>> Installing (14 of 17) dev-lang/python-3.2.3 /tmp/stage1.log:>>> Emerging (72 of 75) dev-lang/python-3.2.3 for /tmp/stage1root/ /tmp/stage1.log:>>> Installing (72 of 75) dev-lang/python-3.2.3 to /tmp/stage1root/ /tmp/stage3.log:>>> Emerging (99 of 189) dev-lang/python-3.2.3 /tmp/stage3.log:>>> Installing (99 of 189) dev-lang/python-3.2.3 So the stage1 seed_update emerge finds sem_open, but the stage1root setup does not. I'm not sure why this would happen, but since the stage3 emerge *does* find sem_open, I'm not sure why the Matplotlib emerge is failing in livecd-stage1. Does anyone want to take a guess? Thanks, Trevor -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
