All of lore.kernel.org
 help / color / mirror / Atom feed
From: <mingli.yu@windriver.com>
To: <meta-virtualization@lists.yoctoproject.org>
Subject: [PATCH] libvirt: Set COMPATIBLE_HOST to 64bit arch
Date: Tue, 16 Jun 2026 02:36:13 -0700	[thread overview]
Message-ID: <20260616093613.1817112-1-mingli.yu@windriver.com> (raw)

From: Mingli Yu <mingli.yu@windriver.com>

qemu sets COMPATIBLE_HOST to 64bit arch [1], so set the COMPATIBLE_HOST
accordingly to fix the build failure.
ERROR: Nothing PROVIDES 'qemu' (but /build/layers/meta-virtualization/recipes-extended/libvirt/libvirt_git.bb DEPENDS on or otherwise requires it)
qemu was skipped: incompatible with host arm-wrs-linux-gnueabi (not in COMPATIBLE_HOST)

[1] https://git.openembedded.org/openembedded-core/commit/?id=f74d4025

Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
---
 recipes-extended/libvirt/libvirt_git.bb | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/recipes-extended/libvirt/libvirt_git.bb b/recipes-extended/libvirt/libvirt_git.bb
index fb7e5293..837f9660 100644
--- a/recipes-extended/libvirt/libvirt_git.bb
+++ b/recipes-extended/libvirt/libvirt_git.bb
@@ -139,6 +139,11 @@ PACKAGECONFIG:remove:mipsarchn32 = "qemu"
 PACKAGECONFIG:remove:mipsarchn64 = "qemu"
 PACKAGECONFIG:remove:powerpc = "qemu"
 PACKAGECONFIG:remove:riscv32 = "qemu"
+# QEMU 11.0.0+ requires 64-bit host architecture
+PACKAGECONFIG:remove:arm = "qemu"
+PACKAGECONFIG:remove:armeb = "qemu"
+PACKAGECONFIG:remove:mipsarch = "qemu"
+PACKAGECONFIG:remove:x86 = "qemu"
 
 # numactl is NOT compatible with arm
 PACKAGECONFIG:remove:arm = "numactl"
-- 
2.54.0



             reply	other threads:[~2026-06-16  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  9:36 mingli.yu [this message]
2026-07-03 13:44 ` [meta-virtualization] [PATCH] libvirt: Set COMPATIBLE_HOST to 64bit arch Bruce Ashfield

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=20260616093613.1817112-1-mingli.yu@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.