From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake -b busted again?
Date: Thu, 11 Aug 2011 12:51:42 +0100 [thread overview]
Message-ID: <1313063502.6733.121.camel@phil-desktop> (raw)
In-Reply-To: <1312982785.14274.381.camel@rex>
On Wed, 2011-08-10 at 14:26 +0100, Richard Purdie wrote:
> On Wed, 2011-08-10 at 11:48 +0100, Phil Blundell wrote:
> > On Wed, 2011-06-29 at 16:11 +0100, Phil Blundell wrote:
> > > Also, it does seem that "bitbake -e -b ..." really is broken. I get:
>
> I've posted a patch to fix this to the bitbake list.
Thanks. I'll give that a try.
p.
next prev parent reply other threads:[~2011-08-11 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 14:48 bitbake -b busted again? Phil Blundell
2011-06-29 14:54 ` Phil Blundell
2011-06-29 14:55 ` Koen Kooi
2011-06-29 15:07 ` Phil Blundell
2011-06-29 15:11 ` Phil Blundell
2011-08-10 10:48 ` Phil Blundell
2011-08-10 13:26 ` Richard Purdie
2011-08-11 11:51 ` Phil Blundell [this message]
2011-08-11 6:44 ` Martin Jansa
2011-08-11 12:03 ` Richard Purdie
2011-08-11 12:21 ` 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=1313063502.6733.121.camel@phil-desktop \
--to=philb@gnu.org \
--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