All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Black <phil.black@hillcrestlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Kernel/module dependencies?
Date: Tue, 17 Mar 2009 16:11:53 -0400	[thread overview]
Message-ID: <1237320713.1422.7.camel@pblack-linux> (raw)

Maybe something is messed up in my configuration, I have a problem with
modules built outside the kernel.  If I update the kernel (including
bumping the recipe revision), other kernel modules do not get rebuilt.
I have a couple of modules whose recipes are set up with lines like:

RDEPENDS += "kernel (${KERNEL_VERSION)"
DEPENDS += "virtual/kernel"

but when the kernel gets updated, the modules do not rebuild.  Is this
just how bitbake works? or is there a way to get modules to rebuild
whenever the kernel updates.  My problem is that when the kernel is
changed, I can no longer load modules built against the previous
revision.  To get things working again, I need to force the rebuild of
anything that depends on the kernel, which is less than ideal.

Thanks in advance,
phil



                 reply	other threads:[~2009-03-17 20:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1237320713.1422.7.camel@pblack-linux \
    --to=phil.black@hillcrestlabs.com \
    --cc=openembedded-devel@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 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.