From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: do_rootfs failure for core-image-sato on mpc8315e-rdb
Date: Thu, 04 Aug 2011 17:31:07 +0100 [thread overview]
Message-ID: <1312475468.6733.6.camel@phil-desktop> (raw)
In-Reply-To: <4E3AC81E.9070709@linux.intel.com>
On Thu, 2011-08-04 at 09:26 -0700, Saul Wold wrote:
> On 08/04/2011 09:13 AM, Richard Purdie wrote:
> > Was this a recent build from scratch? I suspect Koen's recent icon
> > bbclass change and we probably need to ensure hicolor-icon-theme is
> > added do DEPENDS (instead of RDEPENDS like it used to be).
> >
> It seems it's pulled in by gtk-icons.bbclass as an RDEPENDS, should that
> be changed?
If it's an RDEPENDS that's being injected from a python task (other
perhaps than an anonfunc that runs immediately after parsing), it needs
to go in DEPENDS as well. It sounds as though that's the case here.
p.
next prev parent reply other threads:[~2011-08-04 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 15:58 do_rootfs failure for core-image-sato on mpc8315e-rdb Kumar Gala
2011-08-04 16:13 ` Richard Purdie
2011-08-04 16:26 ` Saul Wold
2011-08-04 16:31 ` Phil Blundell [this message]
2011-08-04 18:00 ` Kumar Gala
2011-08-04 16:17 ` Mark Hatle
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=1312475468.6733.6.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