public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] linux-custom: Generate cross linux-libc-dev package
Date: Wed, 10 Sep 2025 15:23:48 +0200	[thread overview]
Message-ID: <3b098b4e-b8b8-474b-8898-901f9f83b283@siemens.com> (raw)
In-Reply-To: <20230830045028.15983-1-ubely@ilbers.de>

On 30.08.23 06:50, Uladzimir Bely wrote:
> In addition to `linux-libc-dev`, install cross-variant of this package
> when "cross" debian profile is enabled.
> 
> This should allow to cross-compile packages depending on custom
> kernel headers with different version than in debian packages.
> Typical case - building bookworm system (with linuix-libc-dev-6.1.*)
> against custom kernel with a lower version (e.g., 5.4).
> 
> With this patch, when such a package is built, debian-provided package
> `linux-libc-dev-<ARCH>-cross` will have an alternative package provided
> by custom linux recipe so that sbuild could replace (downgrade) it.
> 
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
>  meta/recipes-kernel/linux/files/debian/control.tmpl   | 11 +++++++++++
>  .../linux/files/debian/isar/common.tmpl               |  2 ++
>  .../linux/files/debian/isar/install.tmpl              |  3 +++
>  3 files changed, 16 insertions(+)
> 
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index dd0b6245..956db3e3 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -29,6 +29,17 @@ Description: Linux support headers for userspace development
>   This package provides userspaces headers from the Linux kernel.  These headers
>   are used by the installed headers for GNU glibc and other system libraries.
>  
> +Package: linux-libc-dev-${DISTRO_ARCH}-cross
> +Build-Profiles: <!nolibcdev cross>
> +Section: devel
> +Provides: linux-kernel-headers-${DISTRO_ARCH}-cross
> +Architecture: all
> +Description: Linux Kernel Headers for development (for cross-compiling)
> + This package provides headers from the Linux kernel.  These headers
> + are used by the installed headers for GNU glibc and other system
> + libraries. They are NOT meant to be used to build third-party modules for
> + your kernel. Use linux-headers-* packages for that.
> +

No idea why this was missed, but when you actually need the package like
I do now, it's quickly clear what all went wrong here. Fix is being
tested...

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/3b098b4e-b8b8-474b-8898-901f9f83b283%40siemens.com.

  parent reply	other threads:[~2025-09-10 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  4:50 Uladzimir Bely
2023-09-13  5:29 ` Uladzimir Bely
2025-09-10 13:23 ` 'Jan Kiszka' via isar-users [this message]
2025-09-10 15:32   ` '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=3b098b4e-b8b8-474b-8898-901f9f83b283@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=ubely@ilbers.de \
    /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