From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: stefan-koch@siemens.com, jan.kiszka@siemens.com, anaumann@emlix.com
Subject: Re: [PATCH v3 0/4] propagate distro-specific dependencies of arch all packages
Date: Fri, 7 Nov 2025 11:09:03 +0100 [thread overview]
Message-ID: <19985202-434e-4604-825d-35e3b5490805@ilbers.de> (raw)
In-Reply-To: <20251106141122.2887558-1-felix.moessbauer@siemens.com>
v3 LGTM and passed CI.
On 11/6/25 15:11, 'Felix Moessbauer' via isar-users wrote:
> Changes since v2:
>
> Fix root cause of linux-module build errors on cross:
> The previous linux-custom recipe used the cross profile also to control
> which packages are built in a cross setting, which is fundamentally wrong.
> We now split this custom profile off the official one and attach it to the
> cross-profile logic of linux-custom (which refers to "we are in a
> HOST_ARCH != DISTRO_ARCH setting" instead of we are cross-compiling this
> package). The cleanup is done in two stages: First, we properly prefix
> all used custom build profiles according to the build profile spec (p1),
> second we split off the cross profile (p2).
>
> @Stefan: It would be great if you could test this series on your original
> use case.
>
> Best regards,
> Felix
>
> Felix Moessbauer (2):
> linux-custom: prefix profile names according to BuildProfileSpec
> linux-custom: fix name collision on cross profile
> do not add cross profile when building native package
> propagate distro-specific dependencies of arch all packages
>
> meta/classes/dpkg-base.bbclass | 2 +-
> meta/classes/multiarch.bbclass | 10 ++++---
> .../linux/files/debian/control.tmpl | 16 +++++------
> .../linux/files/debian/isar/install.tmpl | 2 +-
> meta/recipes-kernel/linux/linux-custom.inc | 27 ++++++++++++-------
> 5 files changed, 33 insertions(+), 24 deletions(-)
>
--
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/19985202-434e-4604-825d-35e3b5490805%40ilbers.de.
next prev parent reply other threads:[~2025-11-07 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 14:11 'Felix Moessbauer' via isar-users
2025-11-06 14:11 ` [PATCH v3 1/4] linux-custom: prefix profile names according to BuildProfileSpec 'Felix Moessbauer' via isar-users
2025-11-06 16:55 ` 'Jan Kiszka' via isar-users
2025-11-07 8:19 ` 'MOESSBAUER, Felix' via isar-users
2025-11-06 14:11 ` [PATCH v3 2/4] linux-custom: fix name collision on cross profile 'Felix Moessbauer' via isar-users
2025-11-06 14:11 ` [PATCH v3 3/4] do not add cross profile when building native package 'Felix Moessbauer' via isar-users
2025-11-06 14:11 ` [PATCH v3 4/4] propagate distro-specific dependencies of arch all packages 'Felix Moessbauer' via isar-users
2025-11-07 10:09 ` Zhihang Wei [this message]
2025-11-07 10:20 ` [PATCH v3 0/4] " 'MOESSBAUER, Felix' 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=19985202-434e-4604-825d-35e3b5490805@ilbers.de \
--to=wzh@ilbers.de \
--cc=anaumann@emlix.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=stefan-koch@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