Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Nikolas <microvis@cox.net>
To: openembedded-devel@openembedded.org
Subject: BitBake error: "python-native_2.6.1.bb failed"
Date: Tue, 9 Jun 2009 04:01:44 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090609T035246-124@post.gmane.org> (raw)

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
NOTE: Task
failed: /home/nicolae/overo-oe/tmp/work/i686-linux/python-native-2.6.1-
ml3.1/temp/log.do_stage.7641
ERROR: TaskFailed event exception, aborting
ERROR: Build
of /home/nicolae/overo-oe/org.openembedded.dev/recipes/python/python-
native_2.6.1.bb do_populate_staging failed
ERROR: Task 1438 (/home/nicolae/overo-
oe/org.openembedded.dev/recipes/python/python-native_2.6.1.bb, 
do_populate_staging) failed
NOTE: Tasks Summary: Attempted 470 tasks of which 470 didn't need to be rerun 
and 1 failed.
ERROR: '/home/nicolae/overo-oe/org.openembedded.dev/recipes/python/python-
native_2.6.1.bb' failed

Last lines of the log file are:

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. 








             reply	other threads:[~2009-06-09  4:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  4:01 Nikolas [this message]
2009-06-09  6:20 ` BitBake error: "python-native_2.6.1.bb failed" G. Eismann
2009-06-09  7:09   ` Koen Kooi

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=loom.20090609T035246-124@post.gmane.org \
    --to=microvis@cox.net \
    --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