From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
"Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Parsing exception with latest oe-core
Date: Fri, 12 Feb 2016 13:40:47 +0000 [thread overview]
Message-ID: <1455284447.16142.314.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160212132522.GC2607@jama>
On Fri, 2016-02-12 at 14:25 +0100, Martin Jansa wrote:
> On Fri, Feb 12, 2016 at 02:22:22PM +0100, Martin Jansa wrote:
> > On Fri, Feb 12, 2016 at 11:31:10AM +0000, Barros Pena, Belen wrote:
> > >
> > >
> > > On 12/02/2016 10:52, "
> > > openembedded-core-bounces@lists.openembedded.org on
> > > behalf of Martin Jansa" <
> > > openembedded-core-bounces@lists.openembedded.org
> > > on behalf of martin.jansa@gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > >
> > > > is anyone else seeing this unhelpful fatal exception?
> > >
> > > FWIW, I am
> > >
> > > http://piratepad.net/2E3lnayxi8
> > >
> > > Cheers
> >
> > Upgrading bitbake helped here, so it's probably fixed in one of
> > these 2:
> > 4a6a8d0 buildinfohelper: unset brbe variable when build finishes
> > f673079 cooker: gracefully shutdown parsers
> >
> >
> > I wish that the bitbake version and BB_MIN_VERSION were bumped to
> > get
> > more reasonable error message than this unhelpful exception.
>
> This is probably the oe-core change which triggers this behavior, it
> even mentions required bitbake changes in commit message.
>
> RP: Why didn't you bump BB_MIN_VERSION?
I meant to and simply forgot, sorry :(.
Will do this now.
Cheers,
Richard
prev parent reply other threads:[~2016-02-12 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 9:52 Parsing exception with latest oe-core Martin Jansa
2016-02-12 11:31 ` Barros Pena, Belen
2016-02-12 13:22 ` Martin Jansa
2016-02-12 13:25 ` Martin Jansa
2016-02-12 13:40 ` Richard Purdie [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=1455284447.16142.314.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=belen.barros.pena@intel.com \
--cc=martin.jansa@gmail.com \
--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 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.