hey,
I'm investigating enabling AArch32/Virt edk2 builds in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857858
I wanted to see if we can reach a consensus on what the pathname for
these images should be, as these paths for other architectures have
become hardcoded in upstream projects like OpenStack Nova and libvirt.
These project currently expect to find the AArch64 images at:
/usr/share/AAVMF/AAVMF_{CODE,VARS}.fd
And, similarly, the x86-64 images at:
/usr/share/ovmf/OVMF_{CODE,VARS}.fd
I'm unaware of anyone shipping 32-bit x86 images.
I propose:
/usr/share/AAVMF/AAVMF32_{CODE,VARS}.fd
-dann
On Mär 16 2017, Wookey <wookey(a)wookware.org> wrote:
> After feedback from people interested in ILP32, and discussion at
> Linaro Connect, it seems that everyone involved is in agreement that
> the triplets with the 'ilp32' bit in the ABI/OS part rather than the
> machine/cpu part makes more sense. And that we can and should change
> it, so long as it doesn't add significant delay. Thus it was agreed to
> make this change. So the triplet for ilp32 on arm64/aarch64 is now:
>
> aarch64-linux-gnu_ilp32 (normal, little endian)
> aarch64_be-linux-gnu_ilp32 (big endian)
That makes it quite difficult to support building ilp32 packages with
rpm.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab(a)suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
