From: Mike Looijmans <mike.looijmans@topic.nl>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: rootfs fails to build in current master
Date: Sun, 02 Mar 2014 09:21:42 +0100 [thread overview]
Message-ID: <5312EA16.6090403@topic.nl> (raw)
In-Reply-To: <CANyK_8fBSHAtoQ2ZyG4yJK87N42Wn5bb+xHanbvkNw3w7NxEbA@mail.gmail.com>
On 03/01/2014 07:03 PM, Paul Barker wrote:
> On 1 March 2014 17:46, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>> I get this mysterious error at rootfs after updating to current master:
>>
>> Exception: AttributeError: 'module' object has no attribute
>> 'shell_trap_code'
...
>
> As a quick stab-in-the-dark guess: Are you using the current master of
> Bitbake to build this? Each branch of OpenEmbedded has a corresponding
> branch of Bitbake, OE master requires Bitbake master.
That could be the case - though in the past it complained when bitbake
was out of date.
I fetched bitbake's master.
Now I'm getting dozens of fetcher and parser failures, so apparently
something changed in the fetching of repositories.
--
Mike
prev parent reply other threads:[~2014-03-02 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 17:46 rootfs fails to build in current master Mike Looijmans
2014-03-01 18:03 ` Paul Barker
2014-03-02 8:21 ` Mike Looijmans [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=5312EA16.6090403@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.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