From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, stefan-koch@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 1/4] kernel: drop implicit build dependency to build-essential
Date: Mon, 3 Aug 2026 10:34:47 +0200 [thread overview]
Message-ID: <20260803083450.2048909-2-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20260803083450.2048909-1-felix.moessbauer@siemens.com>
This dependency in general should not be explicitly added, as stated in
Debian policy §7.7. By not adding it, we avoid unnecessary dependencies
across cross and native builds by just letting the chroot provide the
right one.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
meta/classes-recipe/linux-kernel.bbclass | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/classes-recipe/linux-kernel.bbclass b/meta/classes-recipe/linux-kernel.bbclass
index 09323e57..ff8b1e61 100644
--- a/meta/classes-recipe/linux-kernel.bbclass
+++ b/meta/classes-recipe/linux-kernel.bbclass
@@ -17,8 +17,7 @@ DISTRIBUTOR ?= "Isar"
# pinned due to known or possible issues with compat 12
DEBIAN_COMPAT:buster = "10"
-KBUILD_DEPENDS ?= "build-essential:native, \
- libelf-dev:native, \
+KBUILD_DEPENDS ?= "libelf-dev:native, \
libncurses-dev:native, \
libssl-dev:native, \
bc, \
--
2.53.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/20260803083450.2048909-2-felix.moessbauer%40siemens.com.
next prev parent reply other threads:[~2026-08-03 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 8:34 [PATCH v2 0/4] Fix kernel build and propagation of linux-libc-dev 'Felix Moessbauer' via isar-users
2026-08-03 8:34 ` 'Felix Moessbauer' via isar-users [this message]
2026-08-03 8:34 ` [PATCH v2 2/4] fix(kernel): restore building " 'Felix Moessbauer' via isar-users
2026-08-03 8:34 ` [PATCH v2 3/4] testsuite: emit output filenames in generate_dependency_graph 'Felix Moessbauer' via isar-users
2026-08-03 8:34 ` [PATCH v2 4/4] testsuite: add test for KERNEL_LIBC_DEV_DEPLOY 'Felix Moessbauer' via isar-users
2026-08-05 8:42 ` [PATCH v2 0/4] Fix kernel build and propagation of linux-libc-dev Zhihang Wei
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=20260803083450.2048909-2-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=stefan-koch@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