From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: BitBake error: "python-native_2.6.1.bb failed"
Date: Tue, 09 Jun 2009 09:09:43 +0200 [thread overview]
Message-ID: <h0l1rn$gld$2@ger.gmane.org> (raw)
In-Reply-To: <200906090820.43460.g.eismann@gmx.net>
On 09-06-09 08:20, G. Eismann wrote:
> On Martes 09 Junio 2009 06:01:44 Nikolas escribió:
>> Hello all,
>>
>> Just started with OE, trying to build first Angstrom distro. After 470
>> tasks completed, bitbake fails as follows:
>
>
>> Compiling /home/nicolae/overo-oe/tmp/work/i686-linux/python-native-2.6.1-
>> ml3.1/temp-staging/home/nicolae/overo-oe/tmp/staging/i686-
>> linux//usr/lib/python2.6/zipfile.py ...
>> make: *** [libinstall] Error 1
>> FATAL: oe_runmake failed
>>
>> Can anybody help, please.
>
> I dont know about the error, but you can use your native python installed in
> your system adding this line to build/conf/local.conf:
> ASSUME_PROVIDED += "python-native"
And then start complaining when various python modules don't build....
prev parent reply other threads:[~2009-06-09 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 4:01 BitBake error: "python-native_2.6.1.bb failed" Nikolas
2009-06-09 6:20 ` G. Eismann
2009-06-09 7:09 ` 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='h0l1rn$gld$2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.