From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Harish Sadineni <Harish.Sadineni@windriver.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [PATCH] populate_sdk_base: add a kernel-src SDK feature
Date: Sun, 30 Aug 2026 16:00:25 -0400 [thread overview]
Message-ID: <20260830200025.4037481-1-twoerner@gmail.com> (raw)
An SDK cannot currently be asked to ship the kernel source, so
kmod.KernelModuleTest skips wherever it runs: it guards on
ensure_target_package("kernel-devsrc") and nothing installs that.
Adding kernel-src to SDK_FEATURES pulls kernel-devsrc into
TOOLCHAIN_TARGET_TASK, alongside the existing go and rust entries.
kernel-devsrc inherits module-base precisely to avoid being multilib
extended, so it is named directly rather than through
multilib_pkg_extend.
[YOCTO #16239]
Suggested-by: Harish Sadineni <Harish.Sadineni@windriver.com>
Suggested-by: Richard Purdie <richard.purdie@linuxfoundation.org>
AI-Generated: codex/claude-opus 5 (xhigh)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
meta/classes-recipe/populate_sdk_base.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes-recipe/populate_sdk_base.bbclass b/meta/classes-recipe/populate_sdk_base.bbclass
index f32e9add019a..2c6dd1828c9c 100644
--- a/meta/classes-recipe/populate_sdk_base.bbclass
+++ b/meta/classes-recipe/populate_sdk_base.bbclass
@@ -79,6 +79,7 @@ TOOLCHAIN_TARGET_TASK ?= " \
${@oe.utils.multilib_pkg_extend(d, 'packagegroup-core-standalone-sdk-target')} \
${@bb.utils.contains('SDK_FEATURES', 'go', oe.utils.multilib_pkg_extend(d, 'packagegroup-go-sdk-target'), '', d)} \
${@bb.utils.contains('SDK_FEATURES', 'rust', oe.utils.multilib_pkg_extend(d, 'libstd-rs'), '', d)} \
+ ${@bb.utils.contains('SDK_FEATURES', 'kernel-src', 'kernel-devsrc', '', d)} \
target-sdk-provides-dummy \
"
TOOLCHAIN_TARGET_TASK_ATTEMPTONLY ?= ""
reply other threads:[~2026-08-30 20:00 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=20260830200025.4037481-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=Harish.Sadineni@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.