From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Joseph Kogut <joseph@anodize.com>,
buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH RESEND] package/qemu: bump to version 11.0.0
Date: Wed, 13 May 2026 13:08:00 +0300 [thread overview]
Message-ID: <877bp7zkov.fsf@tarshish> (raw)
In-Reply-To: <f40ce0c6-0441-4aa0-91a6-fe80a66b2821@gmx.de> (Fiona Klute's message of "Wed, 13 May 2026 12:02:22 +0200")
Hi Fiona,
On Wed, May 13 2026, Fiona Klute wrote:
> Am 13.05.26 um 05:53 schrieb Baruch Siach via buildroot:
>> On Tue, May 12 2026, Joseph Kogut wrote:
>>> Changelog:
>>> https://wiki.qemu.org/ChangeLog/11.0
>>>
>>> Note:
>>> Support for all 32-bit host systems has been removed.
>>>
>>> Signed-off-by: Joseph Kogut <joseph@anodize.com>
>>> ---
>>> package/qemu/Config.in | 5 +----
>>> package/qemu/qemu.hash | 2 +-
>>> package/qemu/qemu.mk | 2 +-
>>> 3 files changed, 3 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/package/qemu/Config.in b/package/qemu/Config.in
>>> index 0b16c8c284..c735381b4b 100644
>>> --- a/package/qemu/Config.in
>>> +++ b/package/qemu/Config.in
>>> @@ -1,11 +1,8 @@
>>> config BR2_PACKAGE_QEMU_ARCH_SUPPORTS_TARGET
>>> bool
>>> # Only tested on these architectures
>>> + default n if !BR2_ARCH_IS_64
>>> default y if BR2_aarch64
>>> - default y if BR2_arm && !BR2_ARM_CPU_ARMV4 && !BR2_ARM_CPU_ARMV5
>>> - default y if BR2_i386
>>> - default y if BR2_mips
>>> - default y if BR2_mipsel
>> qemu 11 dropped 32-bit host support as you mentioned in commit log. But
>> this config symbol indicates target support. qemu changelog does not
>> mention removal of all 32-bit targets.
>
> This is for building Qemu for the (Buildroot) target system though. That makes
> the Buildroot target the (Qemu) host (VMs running on the target), so it's
> affected by Qemu dropping 32-bit host support. The Buildroot host-qemu
> shouldn't be, unless someone is building on a 32-bit system (seems unlikely).
Thanks. I missed that part. I guess the commit log should explain this
host vs target complexity.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-13 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 19:34 [Buildroot] [PATCH RESEND] package/qemu: bump to version 11.0.0 Joseph Kogut
2026-05-13 3:53 ` Baruch Siach via buildroot
2026-05-13 10:02 ` Fiona Klute via buildroot
2026-05-13 10:08 ` Baruch Siach via buildroot [this message]
2026-05-13 16:38 ` Joseph Kogut
2026-05-13 19:36 ` Joseph Kogut
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=877bp7zkov.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=fiona.klute@gmx.de \
--cc=joseph@anodize.com \
--cc=romain.naour@gmail.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