All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Joseph Kogut <joseph@anodize.com>,
	buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
	Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH v3] package/qemu: bump to version 11.0.0
Date: Fri, 15 May 2026 18:03:16 +0200	[thread overview]
Message-ID: <df5404cb93cf7c23fcc27a8aed20a31a@free.fr> (raw)
In-Reply-To: <5b126290-bc03-43ca-b11f-134a828235d9@smile.fr>

Hi Romain,

On 15/05/2026 15:37, Romain Naour via buildroot wrote:
> Hello Joseph,
> 
> Le 14/05/2026 à 22:46, Joseph Kogut a écrit :
>> Changelog:
>> https://wiki.qemu.org/ChangeLog/11.0
>> 
>> Note:
>>   - Support for all 32-bit host systems has been removed.
>>   - Support for microblazeel has been folded into the microblaze 
>> target
>> 
>> Qemu v11.0.0 drops 32-bit support for hosts, all qemu builds must now 
>> be
>> 64-bit. Hosts running 64-bit qemu builds can still emulate 32-bit
>> targets.
>> 
>> Confusingly, the qemu package is also capable of being built and 
>> running
>> on buildroot hosts, and targets. In any case, qemu only supports 
>> running
>> on 64-bit hosts (which may be buildroot targets), so adjust
>> BR2_PACKAGE_QEMU_ARCH_SUPPORTS_TARGET to indicate no support for 
>> 32-bit
>> buildroot targets, and drop configs for architectures like BR2_arm 
>> that
>> are implicitly 32-bit only.
>> 
>> Separately, the qemu microblazeel target was removed with commit
>> 46a25ae3f0e75e230c06e21435850b1cd1c44f07, as the microblaze (qemu)
>> target supports both endiannesses, so that's fixed up in the package
>> Makefile as well.
>> 
>> Signed-off-by: Joseph Kogut <joseph@anodize.com>
> 
> Runtime tested for host-qemu:
> 
> https://gitlab.com/kubu93/buildroot/-/pipelines/2525589698
> 
>> ---
>> Changes in v3:
>> - Update Config.in to properly filter out 32-bit builds [Romain]
>> - Disable downloads from PyPI [Romain]
>> - Add dependencies for host-python-setuptools and host-python-wheel
> 
> I was not sure if it striclty necessary since we disable downloads.
> We follow upstream "Build Information" recommendations:
> 
> https://wiki.qemu.org/ChangeLog/11.0#Build_Information
> 
> "When internet access is not allowed, this functions as a 
> configure-time check
> ensuring that our environment has the necessary minimum viable versions 
> for
> these packaging tools available."
> 
> https://gitlab.com/qemu-project/qemu/-/commit/4e55bb4be53bc7a5e3fe1429af12d2e3090049a5
> 
>> - Reword legacy config to clarify that microblazeel is not dropped
>>   [Romain]
>> - Link to v2: 
>> https://patch.msgid.link/20260513-qemu-v11-0-0-v2-1-de2e8e3c5869@anodize.com
>> 
>> Changes in v2:
>> - Added Config.in comment documenting 64-bit requirement
>> - Expanded commit message to explain 32-bit removal [Baruch]
>> - Fixed build failure with microblazeel target
>> - Added legacy config for microblazeel
>> - Link to v1: 
>> https://patch.msgid.link/20260512-qemu-v11-0-0-v1-1-776ebffbb3af@anodize.com
>> 
>> To: buildroot@buildroot.org
>> Cc: Romain Naour <romain.naour@gmail.com>
>> ---
>>  Config.in.legacy       |  8 ++++++++
>>  package/qemu/Config.in | 12 +-----------
>>  package/qemu/qemu.hash |  2 +-
>>  package/qemu/qemu.mk   | 15 ++++++++++++---
>>  4 files changed, 22 insertions(+), 15 deletions(-)
>> 
>> diff --git a/Config.in.legacy b/Config.in.legacy
>> index ead9ceaa08..90606ebd4b 100644
>> --- a/Config.in.legacy
>> +++ b/Config.in.legacy
>> @@ -146,6 +146,14 @@ endif
>> 
>>  comment "Legacy options removed in 2026.05"
>> 
>> +config BR2_PACKAGE_QEMU_TARGET_MICROBLAZEEL

Since you applied this into the branch "next", this legacy option should 
have
been moved to a new "Legacy options removed in 2026.08" block, right?

>> +	bool "qemu target microblazeel removed"
>> +	select BR2_PACKAGE_QEMU_TARGET_MICROBLAZE
>> +	select BR2_LEGACY
>> +	help
>> +	  Version 11.0.0 of qemu folded microblazeel support into
>> +	  the microblaze target.
>> +
>>  config BR2_KERNEL_HEADERS_6_19
>>  	bool "kernel headers version 6.19.x are no longer supported"
>>  	select BR2_LEGACY

[...]

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-05-15 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 20:46 [Buildroot] [PATCH v3] package/qemu: bump to version 11.0.0 Joseph Kogut
2026-05-15 13:37 ` Romain Naour via buildroot
2026-05-15 16:03   ` Julien Olivain via buildroot [this message]
2026-05-15 16:13     ` Romain Naour via buildroot
2026-05-15 19:21   ` 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=df5404cb93cf7c23fcc27a8aed20a31a@free.fr \
    --to=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --cc=joseph@anodize.com \
    --cc=ju.o@free.fr \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    /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.