From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
isar-users@googlegroups.com, srinuvasan.a@siemens.com
Subject: Re: [PATCH 1/2] linux-custom.inc: drop library dependencies from kernel headers
Date: Fri, 22 Aug 2025 14:29:41 +0200 [thread overview]
Message-ID: <e753accc-815d-451b-a47f-e4a2aec42a87@siemens.com> (raw)
In-Reply-To: <20250822120141.855793-1-Quirin.Gylstorff@siemens.com>
On 22.08.25 14:00, 'Quirin Gylstorff' via isar-users wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> The upstream headers do not have dependencies to the runtime libraries.
> The ${shlibs:Depends} macro will correctly generate the necessary
> dependencies.
>
> libssl is only used in extract-cert which is necessary during the kerneln build
> if CONFIG_SYSTEM_TRUSTED_KEYRING is enabled.
> This config element is not necessary for the module build
> and is therefore removed from the kbuild packages.
>
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
> meta/recipes-kernel/linux/linux-custom.inc | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
> index 01e9bff7..ca90c4e9 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -35,12 +35,7 @@ KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, \
> kmod, \
> linux-base (>= 4.3~),"
>
> -LIBSSL_DEP = "libssl3"
> -LIBSSL_DEP:buster = "libssl1.1"
> -LIBSSL_DEP:bullseye = "libssl1.1"
> -
> -KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, \
> - ${LIBSSL_DEP},"
> +KERNEL_HEADERS_DEBIAN_DEPENDS ?= ""
>
> KERNEL_LIBC_DEV_ARCH_ALL = "0"
> KERNEL_LIBC_DEV_ARCH_ALL:trixie = "1"
Patch ordering: Fix the shlibs thing in patch 2 first so that you can
safely drop the THEN no longer needed header deps.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/e753accc-815d-451b-a47f-e4a2aec42a87%40siemens.com.
prev parent reply other threads:[~2025-08-22 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 12:00 'Quirin Gylstorff' via isar-users
2025-08-22 12:00 ` [PATCH 2/2] linux-custom/d/control.tmpl: correct typo 'Quirin Gylstorff' via isar-users
2025-08-22 12:29 ` 'Jan Kiszka' via isar-users [this message]
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=e753accc-815d-451b-a47f-e4a2aec42a87@siemens.com \
--to=isar-users@googlegroups.com \
--cc=Quirin.Gylstorff@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan.a@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