public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Andreas Naumann' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
	Felix Moessbauer <felix.moessbauer@siemens.com>,
	Andreas Naumann <anaumann@emlix.com>
Subject: [PATCH 2/5] multiarch: handle DPKG_ARCH=all case for transitive deps
Date: Wed,  1 Oct 2025 12:59:26 +0200	[thread overview]
Message-ID: <20251001105929.3731537-3-anaumann@emlix.com> (raw)
In-Reply-To: <20251001105929.3731537-1-anaumann@emlix.com>

From: Felix Moessbauer' via isar-users <isar-users@googlegroups.com>

Arch=all packages might build depend on other arch=all packages, hence we
need to correctly model the dependency chain. Otherwise the transitive
dependencies are built for the distro arch instead of the native arch.

Co-developed-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Co-developed-by: Felix Moessbauer <felix.moessbauer@siemens.com>
Signed-off-by: Andreas Naumann <anaumann@emlix.com>
---
 meta/classes/multiarch.bbclass | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/classes/multiarch.bbclass b/meta/classes/multiarch.bbclass
index babdfbd4..ae465aec 100644
--- a/meta/classes/multiarch.bbclass
+++ b/meta/classes/multiarch.bbclass
@@ -29,7 +29,9 @@ python() {
             d.appendVar('BBCLASSEXTEND', ' compat')
 
     # build native separately only when it differs from the target variant
-    if not archIsAll and archDiffers:
+    # We must not short-circuit for DPKG_ARCH=all packages, as they might
+    # have transitive dependencies which need to be built for -native.
+    if archDiffers:
         d.appendVar('BBCLASSEXTEND', ' native')
     else:
         extend_provides(pn, 'native', d)
-- 
2.43.0

-- 
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/20251001105929.3731537-3-anaumann%40emlix.com.

  parent reply	other threads:[~2025-10-01 10:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 10:59 [RFC 0/5] Improving multiarch support for arch-incompatible packages 'Andreas Naumann' via isar-users
2025-10-01 10:59 ` [PATCH 1/5] rootfs: Do not recursively deploy every dependent package 'Andreas Naumann' via isar-users
2025-10-01 10:59 ` 'Andreas Naumann' via isar-users [this message]
2025-10-01 10:59 ` [PATCH 3/5] image: Do not inherit multiarch 'Andreas Naumann' via isar-users
2025-10-02 12:09   ` 'Jan Kiszka' via isar-users
2025-10-02 14:17     ` 'Andreas Naumann' via isar-users
2025-10-02 14:55       ` 'Jan Kiszka' via isar-users
2025-10-06  7:05         ` 'Andreas Naumann' via isar-users
2025-10-01 10:59 ` [PATCH 4/5] multiarch: Prevent providing incompatible native packages 'Andreas Naumann' via isar-users
2025-10-01 10:59 ` [PATCH 5/5] multiarch: Do not re-extend real -native recipes 'Andreas Naumann' via isar-users
2025-10-02 12:10 ` [RFC 0/5] Improving multiarch support for arch-incompatible packages '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=20251001105929.3731537-3-anaumann@emlix.com \
    --to=isar-users@googlegroups.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=anaumann@emlix.com \
    --cc=felix.moessbauer@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