On 10/10/2016 16:53, Marcin Juszkiewicz wrote:
> W dniu 10.10.2016 o 16:34, Paolo Bonzini pisze:
>> On 10/10/2016 13:30, Sandro Bonazzola wrote:
>
>>> just seen:
>>> DEBUG util.py:421: Error: Package:
>>> 2:qemu-system-aarch64-2.6.1-1.fc24.ppc64le (updates)
>>> DEBUG util.py:421: Requires: edk2-aarch64
>>> DEBUG util.py:421: Error: Package:
>>> 2:qemu-system-x86-2.6.1-1.fc24.ppc64le (updates)
>>> DEBUG util.py:421: Requires: edk2-ovmf
>>>
>>> While installing qemu on ppc64le Fedora.
>>> Any ETA on fixing it?
>>
>> The reason for this is documented in edk2.spec.
>>
>> # actual firmware builds support cross-compiling. edk2-tools
>> # in theory should build everywhere without much trouble, but
>> # in practice the edk2 build system barfs on archs it doesn't know
>> # (such as ppc), so lets limit things to the known-good ones.
>> ExclusiveArch: %{ix86} x86_64 %{arm} aarch64
>>
>> I suppose that QEMU should not require edk2 on architectures other than
>> ARM and x86.
>
> edk2-* packages are noarch. Secondary architectures should imho import
> built binary packages into repository.
It's still a hack to require specific arches to build noarch packages.
For the most important firmware packages (seabios, OVMF, SLOF), we use
cross-compilation so that secondary architectures just work. Some
packages are missing and relying on the firmware exception, but that
should not be done when possible.
The case of edk2 is ugly because the build tools (not the firmware)
require specific architectures. I guess we could easily port them to
PPC64LE, but s390 would still be a mess because they have no testsuite,
unlike for example the ACPI tools where the testsuite helped developing
patches for big-endian support (initially based on Debian and then
fixing things as they came up).
Paolo
> Qemu allows you to emulate several architectures on many architectures -
> basically any Fedora supported one (primary or secondary) on any of them.
> qemu-system-{x86,aarch64,arm,x86-64} may use UEFI binary to run VM.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
