From: "'Tobias Schaffner' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, felix.moessbauer@siemens.com,
amikan@ilbers.de, Tobias Schaffner <tobias.schaffner@siemens.com>
Subject: [PATCH] meta: build the linux-kernels cross libc-dev package if cross-profile is active
Date: Thu, 18 Dec 2025 10:57:05 +0100 [thread overview]
Message-ID: <20251218095705.1234100-1-tobias.schaffner@siemens.com> (raw)
The linux-libc-dev-${DISTRO_ARCH}-cross package is not created when cross
building the kernel because the pkg.${BPN}.cross build profile is only
activated for -native builds with the :cross-pkgs override.
This is an issue for custom kernels, because without the custom cross package,
dependent packages fall back to the default linux-libc-dev, which may lack
custom kernel headers.
Ensure that the cross package is also build for cross-builds when
KERNEL_LIBC_DEV_DEPLOY=1 is set, by adding the pkg.${BPN}.cross profile to the
default BUILD_PROFILES.
Signed-off-by: Tobias Schaffner <tobias.schaffner@siemens.com>
---
meta/classes-recipe/linux-kernel.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/linux-kernel.bbclass b/meta/classes-recipe/linux-kernel.bbclass
index 8f38a617..c9ac3336 100644
--- a/meta/classes-recipe/linux-kernel.bbclass
+++ b/meta/classes-recipe/linux-kernel.bbclass
@@ -126,7 +126,9 @@ BBCLASSEXTEND:append:cross-profile = " kbuildtarget"
# When cross-profile is active:
# build only kernel (including config) with the default variant of the recipe
-BUILD_PROFILES:cross-profile = "pkg.${BPN}.kernel"
+# and build the cross libc-dev package if KERNEL_LIBC_DEV_DEPLOY is enabled
+BUILD_PROFILES:cross-profile = "pkg.${BPN}.kernel \
+ ${@ 'pkg.' + d.getVar('BPN') + '.cross' if bb.utils.to_boolean(d.getVar('KERNEL_LIBC_DEV_DEPLOY')) else '' }"
# -native: kbuild package for host
BUILD_PROFILES:class-native = "pkg.${BPN}.kbuild"
--
2.43.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20251218095705.1234100-1-tobias.schaffner%40siemens.com.
next reply other threads:[~2025-12-18 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 9:57 'Tobias Schaffner' via isar-users [this message]
2025-12-18 10:17 ` 'MOESSBAUER, Felix' via isar-users
2025-12-18 12:13 ` 'Jan Kiszka' via isar-users
2025-12-18 12:27 ` 'Jan Kiszka' via isar-users
2025-12-18 12:39 ` 'Jan Kiszka' via isar-users
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=20251218095705.1234100-1-tobias.schaffner@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=tobias.schaffner@siemens.com \
/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