public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: Cedric Hombourger <cedric.hombourger@siemens.com>,
	Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH] linux-custom: Add missing Multi-Arch foreign to linux-libc-dev*
Date: Tue, 21 Oct 2025 17:22:05 +0200	[thread overview]
Message-ID: <15f02e35-ff1b-4290-aad5-da75812da78c@ilbers.de> (raw)
In-Reply-To: <da68c1eb-7e1c-4dc8-b50b-fd3764ce4fe4@siemens.com>

Applied to next, thanks.

Best regards,
Zhihang

On 9/11/25 21:54, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> This ensures that we create true drop-in replacements of the
> respective upstream packages.
>
> Fixes: 90aa31273278 ("linux-custom: generate linux-libc-dev for "all" vs "any" like trixie")
> Fixes: 13103ab84d5d ("linux-custom: Generate cross linux-libc-dev package")
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>   meta/recipes-kernel/linux/files/debian/control.tmpl | 1 +
>   meta/recipes-kernel/linux/linux-custom.inc          | 2 +-
>   2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index ec0da1ab..e2a878a9 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -36,6 +36,7 @@ Build-Profiles: <!nolibcdev cross !kbuild>
>   Section: devel
>   Provides: linux-kernel-headers-${DISTRO_ARCH}-cross
>   Architecture: all
> +Multi-Arch: foreign
>   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
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
> index 07e49ce7..995279d2 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -224,7 +224,7 @@ def get_additional_build_profiles(d):
>           profiles += ' libcdev-arch-all'
>       return profiles
>   
> -KERNEL_LIBC_DEV_ARCH = "${@ bb.utils.contains('DEB_BUILD_PROFILES', 'libcdev-arch-all', 'all', 'any', d) }"
> +KERNEL_LIBC_DEV_ARCH = "${@ bb.utils.contains('DEB_BUILD_PROFILES', 'libcdev-arch-all', 'all\nMulti-Arch: foreign', 'any', d) }"
>   DEB_BUILD_PROFILES += "${@get_additional_build_profiles(d)}"
>   
>   do_prepare_build:prepend() {

-- 
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/15f02e35-ff1b-4290-aad5-da75812da78c%40ilbers.de.

      reply	other threads:[~2025-10-21 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11 19:54 'Jan Kiszka' via isar-users
2025-10-21 15:22 ` Zhihang Wei [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=15f02e35-ff1b-4290-aad5-da75812da78c@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=cedric.hombourger@siemens.com \
    --cc=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