All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] image.bbclass: depends on virtual/kernel
Date: Fri, 22 Nov 2013 12:06:29 +0000	[thread overview]
Message-ID: <1385121989.16887.157.camel@ted> (raw)
In-Reply-To: <1385120462.15760.33.camel@phil-desktop.brightsign>

On Fri, 2013-11-22 at 11:41 +0000, Phil Blundell wrote:
> On Fri, 2013-11-22 at 13:39 +0800, Qi.Chen@windriver.com wrote:
> > Add 'virtual/kernel' to DEPENDS in image.bbclass so that the kernel
> > can get built by default. Otherwise, the kernel will not get built
> > unless it's required by other packages like v86d. As a result, if
> > we build 'core-image-minimal' for qemumips, the kernel is not built,
> > and we have 'bitbake linux-yocto' before we can use runqemu to start
> > the target.
> 
> Not all images do actually need a kernel, and this will cause a
> dependency loop for old-style initramfs images that are dependencies of
> virtual/kernel itself.
> 
> If you just want to ensure that the kernel is available at deployment
> time, perhaps you could make virtual/kernel be a dependency of do_deploy
> specifically (rather than do_configure as you have it here).
> Alternatively, if this is a specific problem for core-image-minimal,
> maybe the virtual/kernel dependency should just go in there.

I think it just happens that core-image-minimal doesn't install any
kernel modules so shows the symptoms.

The best thing to do here is probably have a dependency on specifically
on virtual/kernel:do_deploy since anyone building an image would usually
want to trigger that. I appreciate there are some cases where you
wouldn't but those are in a minority.

Cheers,

Richard



  reply	other threads:[~2013-11-22 12:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  5:39 [PATCH 0/1] image.bbclass: depends on virtual/kernel Qi.Chen
2013-11-22  5:39 ` [PATCH 1/1] " Qi.Chen
2013-11-22 11:38   ` Martin Jansa
2013-11-22 11:41   ` Phil Blundell
2013-11-22 12:06     ` Richard Purdie [this message]
2013-11-22 19:58   ` Otavio Salvador
2013-11-22 22:32     ` Andrea Adami
2013-11-25 12:09       ` ChenQi
2013-11-25 12:28         ` Otavio Salvador
2013-11-25 12:57           ` Richard Purdie

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=1385121989.16887.157.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.