From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] sem_open inconsistency in installed Python versions
Date: Mon, 11 Mar 2013 07:55:43 -0400 [thread overview]
Message-ID: <20130311115543.GE7445@odin.tremily.us> (raw)
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-03-11 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130311115543.GE7445@odin.tremily.us \
--to=wking@tremily.us \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox