public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: isar-users@googlegroups.com
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH] fix: improve check for availability of compat arch
Date: Mon,  6 Mar 2023 08:12:26 +0100	[thread overview]
Message-ID: <20230306071226.3165673-1-adriaan.schmidt@siemens.com> (raw)

follow-up to 3aa4d3832ccb2271e850a8245cb45ad40e3da366

The check, whether compat can be built needs to also ensure that we
actually have a compat arch for our DISTRO_ARCH. There is a helper
function in the compat class for this now.

Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>

---
Sorry, I was slow to send an updated patch, rebasing the essential
packages feature onto v4 of the multiarch series.

Adriaan
---
 meta/classes/essential.bbclass | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/classes/essential.bbclass b/meta/classes/essential.bbclass
index be98a76d..2ae31b38 100644
--- a/meta/classes/essential.bbclass
+++ b/meta/classes/essential.bbclass
@@ -3,9 +3,11 @@
 
 ISAR_REBUILD_ESSENTIAL_PKGS ?= ""
 
+inherit compat
+
 python() {
     isar_rebuild_essential_pkgs = (d.getVar('ISAR_REBUILD_ESSENTIAL_PKGS') or '').split()
-    build_compat = d.getVar('ISAR_ENABLE_COMPAT_ARCH') == "1"
+    build_compat = isar_can_build_compat(d)
     build_native = not d.getVar('DISTRO_ARCH') == d.getVar('HOST_ARCH')
 
     # construct list of essential packages that should be rebuilt:
-- 
2.30.2


             reply	other threads:[~2023-03-06  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  7:12 Adriaan Schmidt [this message]
2023-03-09  5:44 ` Uladzimir Bely

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=20230306071226.3165673-1-adriaan.schmidt@siemens.com \
    --to=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.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