From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH-for-10.2] roms: Do not try to build EDK2 for 32-bit ARM on Fedora
Date: Tue, 18 Nov 2025 12:17:50 +0100 [thread overview]
Message-ID: <038c229c-2b94-4294-a73b-093b74030838@linaro.org> (raw)
In-Reply-To: <vnutsclexonswf5dv2nx5qjp3v2k5gtcpkseqhvojtjbeag2f5@q7i2zxhw5r4z>
On 18/11/25 08:09, Gerd Hoffmann wrote:
> On Mon, Nov 17, 2025 at 03:04:20PM +0100, Philippe Mathieu-Daudé wrote:
>> With Fedora 27, support for 32-bit ARM hosts was dropped.
>> QEMU also stopped building the docker images in commit
>> 0054dc8bde4 ("Update lcitool and fedora to 37").
>
> /me fails to see the link to the patch ...
>
> This is about the /guest/ firmware images, and they are
> cross-compiled. And note that you can run 32-bit guests
> on 64-bit hosts (if supported by the cpu).
>
> Note that I have no objections to removing the 32-bit edk2
> firmware images. Upstream edk2 is in the process of removing
> 32-bit support, so that is going to happen sooner or later
> anyway (for both arm and ia32). Also UEFI on 32-bit never
> really took off in the first place.
>
> But when doing so do it properly please. Remove build config
> (in edk2-build.config), pre-built binaries, maybe also test
> cases, ...
I only have handy Fedora 42 and 43 VMs where this script doesn't
work anymore. I'm not really interested in installing a pre-37
Fedora to build EDK2 ARM, nor motivated right now to clean this
"properly". Better we wait EDK2 32-bit removal upstream and then
clean these QEMU scripts.
Regards,
Phil.
prev parent reply other threads:[~2025-11-18 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 14:04 [PATCH-for-10.2] roms: Do not try to build EDK2 for 32-bit ARM on Fedora Philippe Mathieu-Daudé
2025-11-18 7:09 ` Gerd Hoffmann
2025-11-18 11:17 ` Philippe Mathieu-Daudé [this message]
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=038c229c-2b94-4294-a73b-093b74030838@linaro.org \
--to=philmd@linaro.org \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).