public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Quirin Gylstorff' via isar-users" <isar-users@googlegroups.com>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH 1/8] meta/recipes-kernel/linux: Use proper SSL toolkit (libssl3t64) for Trixie
Date: Thu, 21 Aug 2025 13:28:40 +0200	[thread overview]
Message-ID: <b9f497bc-68e9-4d09-9e1d-05d38399a716@siemens.com> (raw)
In-Reply-To: <20250816105921.3428140-2-srinuvasan.a@siemens.com>



On 8/16/25 12:59, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
> 
> Custom kernel recipe builds were failing on Trixie due to a dependency
> on the unavailable libssl3 package. Updated to use the correct
> libssl3t64 package for Trixie builds.
> 
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
>   meta/recipes-kernel/linux/linux-custom.inc | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
> index 01e9bff7..f55e2f29 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -35,9 +35,10 @@ 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"
> +LIBSSL_DEP:bookworm = "libssl3"
> +LIBSSL_DEP = "libssl3t64"

 >   >   KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, \
>                                     ${LIBSSL_DEP},"


The kernel_headers should not have any dependency to libc6 or libssl*. 
As the header package does not contain any binary which uses libssl3/libc6.

In Debian upstream libssl is used by the Kbuild package. After my 
current analysis the binary dependency is missing in ISAR as the macro 
${shlibs:Depends} does not add the dependency.

Quirin

-- 
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/b9f497bc-68e9-4d09-9e1d-05d38399a716%40siemens.com.

  reply	other threads:[~2025-08-21 11:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 10:59 [PATCH 0/8] Add Trixie support for various machines srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 1/8] meta/recipes-kernel/linux: Use proper SSL toolkit (libssl3t64) for Trixie srinuvasan.a via isar-users
2025-08-21 11:28   ` 'Quirin Gylstorff' via isar-users [this message]
2025-08-21 11:53     ` Srinuvasan Arjunan
2025-08-21 12:46       ` 'Quirin Gylstorff' via isar-users
2025-08-16 10:59 ` [PATCH 2/8] Add trixie support for virtualbox srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 3/8] Add trixie support for bananapi srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 4/8] Add trixie support for de0-nano-soc srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 5/8] Add nanopi-neo-trixie target srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 6/8] meta-isar: Add phyboard-mira-trixie target srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 7/8] meta-isar: Enable hikey support on Trixie srinuvasan.a via isar-users
2025-08-16 10:59 ` [PATCH 8/8] Add trixie support for container-amd64 srinuvasan.a 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=b9f497bc-68e9-4d09-9e1d-05d38399a716@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=quirin.gylstorff@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