From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Arulpandiyan Vadivel <arulcse2008@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: support to add linux-libc-dev package with kernel name
Date: Thu, 11 Sep 2025 13:05:37 +0200 [thread overview]
Message-ID: <ac0068a2-af5a-43a8-945f-568739f840e0@siemens.com> (raw)
In-Reply-To: <34bc7c07-25ca-4375-8ca5-dcbdc3bdcbf0@siemens.com>
On 11.09.25 10:33, Jan Kiszka wrote:
> On 11.09.25 07:38, Arulpandiyan Vadivel wrote:
>> I understand the issue reported , Can you please help to share/provide
>> the steps to reproduce the issue where I can check for the solutions
>>
>
> 1. Fix all the urgent mistakes of the patch:
>
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index a79b86c4..6a4866da 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -36,9 +36,9 @@ Description: Linux support headers for userspace development
> Package: linux-libc-dev-${DISTRO_ARCH}-cross-${KERNEL_NAME_PROVIDED}
> Build-Profiles: <!nolibcdev cross !kbuild>
> Section: devel
> -Conflicts: linux-kernel-headers-${DISTRO_ARCH}-cross
> -Provides: linux-kernel-headers-${DISTRO_ARCH}-cross
> -Replaces: linux-kernel-headers-${DISTRO_ARCH}-cross
> +Conflicts: linux-libc-dev-${DISTRO_ARCH}-cross
> +Provides: linux-kernel-headers-${DISTRO_ARCH}-cross, linux-libc-dev-${DISTRO_ARCH}-cross
> +Replaces: linux-libc-dev-${DISTRO_ARCH}-cross
> Architecture: all
> Description: Linux Kernel Headers for development (for cross-compiling)
> This package provides headers from the Linux kernel. These headers
> diff --git a/meta/recipes-kernel/linux/files/debian/isar/common.tmpl b/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> index b004214f..83505fda 100644
> --- a/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> @@ -9,7 +9,7 @@ ARCH=${KERNEL_ARCH}
> KERNEL_PKG_IMAGE=linux-image-${KERNEL_NAME_PROVIDED}
> KERNEL_PKG_KERN_HEADERS=linux-headers-${KERNEL_NAME_PROVIDED}
> KERNEL_PKG_LIBC_HEADERS=linux-libc-dev-${KERNEL_NAME_PROVIDED}
> -KERNEL_PKG_LIBC_HEADERS_CROSS=linux-libc-dev-${DISTRO_ARCH}-cross
> +KERNEL_PKG_LIBC_HEADERS_CROSS=linux-libc-dev-${DISTRO_ARCH}-cross-${KERNEL_NAME_PROVIDED}
> KERNEL_PKG_KERN_KBUILD=linux-kbuild-${KERNEL_NAME_PROVIDED}
> KERNEL_PKG_KERN_KBUILD_CROSS=${KERNEL_PKG_KERN_KBUILD}-${DISTRO_ARCH}-cross
>
>
> 2. Build a kernel that has KERNEL_LIBC_DEV_DEPLOY = "1"
>
> 3. Build another packages and check if the self-built linux-libc-dev (-cross) is pulled into the sbuild-chroot
>
> I got some idea how the latter could possible be restored, even when using libc-dev packages with different names. Will try that out later.
>
...but it did not work so far: I tried to inject an explicit build
dependency on linux-libc-dev into every package build, but I had to
weaken it because KERNEL_LIBC_DEV_DEPLOY is generally off - or there is
even no custom kernel.
diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
index 0e5a495d..149e8577 100644
--- a/meta/classes/dpkg.bbclass
+++ b/meta/classes/dpkg.bbclass
@@ -115,6 +115,7 @@ dpkg_runbuild() {
--no-run-lintian --no-run-piuparts --no-run-autopkgtest --resolve-alternatives \
--bd-uninstallable-explainer=apt \
--no-apt-update --apt-distupgrade \
+ --add-depends="linux-libc-dev|linux-libc-dev-${PACKAGE_ARCH}-cross|linux-libc-dev-${KERNEL_NAME}|linux-libc-dev-${PACKAGE_ARCH}-cross-${KERNEL_NAME}" \
--chroot-setup-commands="echo \"Package: *\nPin: release n=${DEBDISTRONAME}\nPin-Priority: 1000\" > /etc/apt/preferences.d/isar-apt" \
--chroot-setup-commands="echo \"APT::Get::allow-downgrades 1;\" > /etc/apt/apt.conf.d/50isar-apt" \
--chroot-setup-commands="rm -f /var/log/dpkg.log" \
But this still does not trigger any automatic updates/downgrades to the
self-built libc-dev.
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/ac0068a2-af5a-43a8-945f-568739f840e0%40siemens.com.
next prev parent reply other threads:[~2025-09-11 11:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 19:00 'Arulpandiyan Vadivel' via isar-users
2025-01-12 20:46 ` 'cedric.hombourger@siemens.com' via isar-users
2025-01-13 8:07 ` [PATCH V2] " 'Arulpandiyan Vadivel' via isar-users
2025-01-13 14:04 ` 'cedric.hombourger@siemens.com' via isar-users
2025-01-14 16:33 ` [PATCH V3] " 'Arulpandiyan Vadivel' via isar-users
2025-01-17 13:25 ` 'Jan Kiszka' via isar-users
2025-01-17 17:37 ` 'Arulpandiyan Vadivel' via isar-users
2025-01-17 17:40 ` 'Jan Kiszka' via isar-users
2025-01-17 17:44 ` 'Jan Kiszka' via isar-users
2025-01-17 17:59 ` 'Arulpandiyan Vadivel' via isar-users
2025-01-17 18:02 ` [PATCH V4] " 'Arulpandiyan Vadivel' via isar-users
2025-01-21 9:47 ` [PATCH] " 'Arulpandiyan Vadivel' via isar-users
2025-02-06 11:50 ` 'Vadivel, Arulpandiyan' via isar-users
2025-02-07 7:48 ` Uladzimir Bely
2025-09-10 13:55 ` 'Jan Kiszka' via isar-users
2025-09-10 17:22 ` 'Jan Kiszka' via isar-users
2025-09-11 5:11 ` 'Jan Kiszka' via isar-users
2025-09-11 5:21 ` Arulpandiyan Vadivel
2025-09-11 5:28 ` 'Jan Kiszka' via isar-users
2025-09-11 5:38 ` Arulpandiyan Vadivel
2025-09-11 8:33 ` 'Jan Kiszka' via isar-users
2025-09-11 11:05 ` 'Jan Kiszka' via isar-users [this message]
2025-09-11 13:59 ` 'Jan Kiszka' via isar-users
2025-09-11 7:02 ` 'cedric.hombourger@siemens.com' 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=ac0068a2-af5a-43a8-945f-568739f840e0@siemens.com \
--to=isar-users@googlegroups.com \
--cc=arulcse2008@gmail.com \
--cc=jan.kiszka@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