From: "'cedric.hombourger@siemens.com' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Vadivel, Arulpandiyan" <arulpandiyan.vadivel@siemens.com>
Cc: "srikanth.krishnakar@siemens.com" <srikanth.krishnakar@siemens.com>
Subject: Re: [PATCH] linux-custom: generate linux-libc-dev package for all arch
Date: Fri, 3 Jan 2025 08:23:15 +0000 [thread overview]
Message-ID: <1fa6cdbf38bbc64633714fbafe2dfc987ffac209.camel@siemens.com> (raw)
In-Reply-To: <20250103072928.45916-1-arulpandiyan.vadivel@siemens.com>
On Fri, 2025-01-03 at 12:59 +0530, Arulpandiyan Vadivel wrote:
> Generate linux-libc-dev package for all architecture instead of
for the "all" architecture
> desired machine architecture.
>
> With this patch, when upstream Kernels is build above 6.11, It helps
Avoid "This patch", "This commit" in commit logs
Where are you checking for kernel version >= 6.11, this appears to be
missing in your patch and will likely break builds with kernels < 6.11
Make sure no arch-dependent headers are included in our linux-libc-dev
package. In linux-libc-dev packages built in my trees, I see header
files in e.g. usr/include/x86_64-linux-gnu
We may need to make more changes for our packages to match those now
generated by Debian
> to align with bookworm-backports, trixie versions of linux-libc-dev.
>
> This change also fixes to build failures with libc6-dev dependencies
> as below
> for upstream stable kernel 6.12.
> > Broken libc6-dev:arm64 Depends on linux-libc-dev:arm64 < none @un
> > pH >
> > Considering linux-libc-dev:arm64 1 as a solution to libc6-
> > dev:arm64 10001
> > Considering linux-libc-dev:arm64 1 as a solution to libc6-
> > dev:arm64 10001
> > Done
did you run the Isar test suite to validate your changes prior to
submitting?
>
> Signed-off-by: Arulpandiyan Vadivel
> <arulpandiyan.vadivel@siemens.com>
> ---
> meta/recipes-kernel/linux/files/debian/control.tmpl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl
> b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index 04ad0f4f..cc9cbd44 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -26,7 +26,7 @@ Package: linux-libc-dev
> Build-Profiles: <!nolibcdev kernel>
> Section: devel
> Provides: linux-kernel-headers
> -Architecture: any
> +Architecture: all
> 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.
--
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/1fa6cdbf38bbc64633714fbafe2dfc987ffac209.camel%40siemens.com.
next prev parent reply other threads:[~2025-01-03 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 7:29 'Arulpandiyan Vadivel' via isar-users
2025-01-03 8:23 ` 'cedric.hombourger@siemens.com' via isar-users [this message]
2025-01-04 19:08 ` [PATCH v2] linux-custom: generate linux-libc-dev for "all" vs "any" like trixie 'Cedric Hombourger' via isar-users
2025-01-16 7:01 ` Uladzimir Bely
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=1fa6cdbf38bbc64633714fbafe2dfc987ffac209.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=arulpandiyan.vadivel@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=srikanth.krishnakar@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