public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
	Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
	"Schaffner,
	Tobias (FT RPD CED OES-DE)" <tobias.schaffner@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "amikan@ilbers.de" <amikan@ilbers.de>,
	"Koch, Stefan (DI PA DCP R&D 3)" <stefan-koch@siemens.com>
Subject: Re: [PATCH] meta: build the linux-kernels cross libc-dev package if cross-profile is active
Date: Thu, 18 Dec 2025 13:27:01 +0100	[thread overview]
Message-ID: <65b7d8dc-8ac1-48ec-8d1c-59dfbcf7741b@siemens.com> (raw)
In-Reply-To: <4434b4a1-6433-418d-9f1b-a41a51d2cc19@siemens.com>

On 18.12.25 13:13, 'Jan Kiszka' via isar-users wrote:
> On 18.12.25 11:17, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
>> On Thu, 2025-12-18 at 10:57 +0100, Tobias Schaffner wrote:
>>> The linux-libc-dev-${DISTRO_ARCH}-cross package is not created when cross
>>> building the kernel because the pkg.${BPN}.cross build profile is only
>>> activated for -native builds with the :cross-pkgs override.
>>>
>>> This is an issue for custom kernels, because without the custom cross package,
>>> dependent packages fall back to the default linux-libc-dev, which may lack
>>> custom kernel headers.
>>>
>>> Ensure that the cross package is also build for cross-builds when
>>> KERNEL_LIBC_DEV_DEPLOY=1 is set, by adding the pkg.${BPN}.cross profile to the
>>> default BUILD_PROFILES.
>>
> 
> Testing this now as well. Thanks already!
> 
>> Hi,
>>
>> this issue probably was found on the xenomai-images layer. As this is
>> the second or third time we have issues on the libc-dev dependency
>> chain, we definitely need a test.
>>
> 
> Yes, we need that. I wasn't updating xenomai-images for a while, so I
> didn't catch the regression this way.
> 
>> Please also try to find the commit that broke it and add a fixes tag.
>>
> 
> Most likely afba99fe6aeb7d4aae1209e37d1f64458b31f62e.
> 
> Jan
> 

BTW, we also still have an issues with multiple providers for linux-libc-dev and -cross at bitbake level, e.g.:

 NOTE: Multiple providers are available for linux-libc-dev-armhf-cross (linux-xenomai-4, linux-xenomai-4-kbuildtarget)
Consider defining a PREFERRED_PROVIDER entry to match linux-libc-dev-armhf-cross

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/65b7d8dc-8ac1-48ec-8d1c-59dfbcf7741b%40siemens.com.

  reply	other threads:[~2025-12-18 12:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18  9:57 'Tobias Schaffner' via isar-users
2025-12-18 10:17 ` 'MOESSBAUER, Felix' via isar-users
2025-12-18 12:13   ` 'Jan Kiszka' via isar-users
2025-12-18 12:27     ` 'Jan Kiszka' via isar-users [this message]
2025-12-18 12:39 ` '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=65b7d8dc-8ac1-48ec-8d1c-59dfbcf7741b@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=stefan-koch@siemens.com \
    --cc=tobias.schaffner@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