From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake -b busted again?
Date: Wed, 29 Jun 2011 15:54:53 +0100 [thread overview]
Message-ID: <1309359293.2551.49.camel@phil-desktop> (raw)
In-Reply-To: <1309358918.2551.48.camel@phil-desktop>
On Wed, 2011-06-29 at 15:48 +0100, Phil Blundell wrote:
> Using bitbake master from today, I'm now getting this error whenever I
> try to do "bitbake -b anything.bb":
Actually, it looks like I was just unlucky/unskilled in my choice of
recipes when I tested. It does in fact work for at least some files;
there must be something about the ones I was trying to begin with that
is upsetting it. I'll investigate further.
p.
next prev parent reply other threads:[~2011-06-29 14:58 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 [this message]
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
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=1309359293.2551.49.camel@phil-desktop \
--to=pb@pbcl.net \
--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