From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] classes/sanity: fix handling of bblayers.conf updating
Date: Fri, 12 Apr 2013 22:30:42 +0100 [thread overview]
Message-ID: <1365802242.16702.71.camel@ted> (raw)
In-Reply-To: <20130412211005.GY2477@jama>
On Fri, 2013-04-12 at 23:10 +0200, Martin Jansa wrote:
> On Fri, Apr 12, 2013 at 09:16:51PM +0100, Paul Eggleton wrote:
> > Fix the fairly long-standing problem of treating a newer bblayers.conf
> > in the same manner as an older one (reporting that it had been updated
> > even if nothing was done). The recent work to do a reparse without
> > having to manually re-run bitbake turned this from an annoyance into an
> > endless loop, so it had to be fixed.
>
> Is this endless loop, bitbake hanging forever while parsing or was it
> showing something or failing soon with endless loop detected by python?
You'd see nothing at all, you'd run "bitbake X" and it would just sit
there indefinitely in a loop.
It could be triggered by including meta-yocto but not setting
DISTRO=poky* in a build dir where DISTRO=poky* has previously been used.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-12 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 20:16 [PATCH 0/1] Fix handling of bblayers.conf updating Paul Eggleton
2013-04-12 20:16 ` [PATCH 1/1] classes/sanity: fix " Paul Eggleton
2013-04-12 21:10 ` Martin Jansa
2013-04-12 21:30 ` Richard Purdie [this message]
2013-04-16 17:09 ` Martin Jansa
2013-04-16 21:06 ` Richard Purdie
2013-04-16 21:41 ` Martin Jansa
2013-04-16 23:25 ` Paul Eggleton
2013-04-17 7:01 ` Richard Purdie
2013-04-17 8:54 ` Martin Jansa
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=1365802242.16702.71.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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