Re: [PATCH] linux-custom: support to add linux-libc-dev package with kernel name

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 11.09.25 13:05, Jan Kiszka wrote:
> 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.
> 

We further discussed this internally, and I played around with an
artificial test setup as well: It seems more and more unlikely that one
can replace an upstream Debian package with one that is differently
called and only provides the upstream name. Even with the preferences we
configure, dpkg will still prefer the upstream packages over such a
replacement when resolving dependencies.

Only if anyone can solve that problem above, we would be able to support
multiple libc-dev packages in the same build run. For now, I will create
a revert patch and propose to roll everything back to single, unified
linux-libc-dev per build in isar.

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/fad842e5-ff13-4a77-9861-ea72eda373db%40siemens.com.