From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] kernel: set COMPATIBLE_HOST to *-linux
Date: Fri, 11 Dec 2020 08:53:45 -0800 [thread overview]
Message-ID: <51192976-54f1-a6dc-6be0-0780c3006338@gmail.com> (raw)
In-Reply-To: <20201211160922.4125554-1-ross.burton@arm.com>
On 12/11/20 8:09 AM, Ross Burton wrote:
> The target system triple contains whether the target is Linux or not,
> so use it to avoid situations where you can attempt to build a kernel
> for systems which don't support Linux.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
> meta/classes/kernel.bbclass | 2 ++
> meta/recipes-kernel/linux/linux-dummy.bb | 2 +-
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 1a444efabf..2f1006ddf0 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -1,5 +1,7 @@
> inherit linux-kernel-base kernel-module-split
>
> +COMPATIBLE_HOST = ".*-linux"
does this cover linux-gnueabi and such tuples too ?
> +
> KERNEL_PACKAGE_NAME ??= "kernel"
> KERNEL_DEPLOYSUBDIR ??= "${@ "" if (d.getVar("KERNEL_PACKAGE_NAME") == "kernel") else d.getVar("KERNEL_PACKAGE_NAME") }"
>
> diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-kernel/linux/linux-dummy.bb
> index 649fc04dd1..95dc85ff2f 100644
> --- a/meta/recipes-kernel/linux/linux-dummy.bb
> +++ b/meta/recipes-kernel/linux/linux-dummy.bb
> @@ -26,7 +26,7 @@ DESCRIPTION_kernel-vmlinux = "Kernel vmlinux meta package"
>
> INHIBIT_DEFAULT_DEPS = "1"
>
> -#COMPATIBLE_MACHINE = "your_machine"
> +COMPATIBLE_HOST = ".*-linux"
>
> PR = "r1"
>
>
>
>
>
>
next prev parent reply other threads:[~2020-12-11 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 16:09 [PATCH] kernel: set COMPATIBLE_HOST to *-linux Ross Burton
2020-12-11 16:53 ` Khem Raj [this message]
2020-12-13 22:20 ` [OE-core] " Ross Burton
2020-12-13 23:09 ` Richard Purdie
2020-12-16 10:39 ` Ross Burton
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=51192976-54f1-a6dc-6be0-0780c3006338@gmail.com \
--to=raj.khem@gmail.com \
--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