From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: python 'platform' module not being built
Date: Wed, 04 Feb 2009 21:57:27 +0100 [thread overview]
Message-ID: <gmcvfn$ahd$1@ger.gmane.org> (raw)
In-Reply-To: <gmcu6b$5r9$1@ger.gmane.org>
On 04-02-09 21:35, Koen Kooi wrote:
> Hi,
>
> Frans and I are trying to get python-coherence working, but we are
> hitting a few snags:
>
> root@beagleboard:~# coherence
> Traceback (most recent call last):
> File "/usr/bin/coherence", line 21, in <module>
> from coherence import __version__
> File "/usr/lib/python2.6/site-packages/coherence/__init__.py", line 1,
> in <module>
> import platform
> ImportError: No module named platform
> root@beagleboard:~#
>
> Some googling brings me to:
>
> http://docs.python.org/library/platform.html
>
> That suggests that it's part of python, but it doesn't seem to get built
> in OE, is there any reason for that? If not, what would be the best way
> to build it?
Ignore more, it's in python-misc (which doesn't get dragged in by 'opkg
install python-modules')
regards,
Koen
prev parent reply other threads:[~2009-02-04 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 20:35 python 'platform' module not being built Koen Kooi
2009-02-04 20:57 ` Koen Kooi [this message]
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='gmcvfn$ahd$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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