From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: List of bbappends without matching recipes
Date: Thu, 9 Jun 2011 16:31:48 +0100 [thread overview]
Message-ID: <201106091631.48506.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <233337C7-346F-4E05-887C-776008F90E5F@dominion.thruhere.net>
On Thursday 09 June 2011 16:15:49 Koen Kooi wrote:
> I ran bitbake layers on a stock angstrom setup and it reported a lot of
> 'broken' bbappends:
I've recently submitted a patch to bitbake-devel which fixes bitbake-layers'
handling of skipped recipes so that it doesn't report them as missing. I don't
think skipped recipes can account for that entire list however.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-09 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 15:15 List of bbappends without matching recipes Koen Kooi
2011-06-09 15:24 ` Bruce Ashfield
2011-06-09 15:32 ` Koen Kooi
2011-06-09 15:28 ` Phil Blundell
2011-06-09 15:31 ` Paul Eggleton [this message]
2011-06-09 15:54 ` Paul Eggleton
2011-06-09 16:02 ` Martin Jansa
2011-06-09 16:35 ` Chris Larson
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=201106091631.48506.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.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