From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: provide virtual/kernel-${PV}
Date: Fri, 11 Feb 2011 14:18:21 +0100 [thread overview]
Message-ID: <ij3cut$mts$1@dough.gmane.org> (raw)
In-Reply-To: <1297429349-5526-1-git-send-email-obi@opendreambox.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-02-11 14:02, Andreas Oberritter wrote:
> * Allow precompiled modules to depend on a specific kernel version.
>
> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
> ---
> classes/kernel.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/classes/kernel.bbclass b/classes/kernel.bbclass
> index 0d1b4ad..55e3ca0 100644
> --- a/classes/kernel.bbclass
> +++ b/classes/kernel.bbclass
> @@ -1,6 +1,6 @@
> inherit linux-kernel-base module_strip
>
> -PROVIDES += "virtual/kernel"
> +PROVIDES += "virtual/kernel virtual/kernel-${PV}"
> DEPENDS += "virtual/${TARGET_PREFIX}gcc virtual/${TARGET_PREFIX}depmod-${@get_kernelmajorversion('${PV}')} virtual/${TARGET_PREFIX}gcc${KERNEL_CCSUFFIX} update-modules bluez-dtl1-workaround"
>
> # we include gcc above, we dont need virtual/libc
How is PV know before the kernel is built? The line below has a
workaround for that, so I guess it also needs one in PROVIDES, no?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNVTcdMkyGM64RGpERAqZtAJ9gV1L+A2Ph+3aH1/aKr9PGlUeQCwCcCUUE
TlXU4/M8l7ycdmwm+7a8VL0=
=JO+0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-11 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 13:02 [PATCH] kernel.bbclass: provide virtual/kernel-${PV} Andreas Oberritter
2011-02-11 13:18 ` Koen Kooi [this message]
2011-02-11 13:25 ` Andreas Oberritter
2011-02-22 0:42 ` Andreas Oberritter
2011-02-22 2:00 ` Tom Rini
2011-02-22 2:51 ` Andreas Oberritter
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='ij3cut$mts$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.