On 04/29/2016 06:58 PM, Steve McIntyre wrote: > On Fri, Apr 29, 2016 at 06:20:55PM +0200, pollux wrote: >> Indeed, on PC architectures, EFI executables are 64-bits EXE files. > > Ummm, what? 32-bit i386 (ia32) should be supported just fine. If it's > not working, that's just a bug.
I'm talking about .efi files. If your firmware (BIOS) is 64-bits, then your executables can only use a 64-bits ABI for boot/runtime services. IA32 EFI firmwares are only used by some low-end platforms, or some embedded platforms (Intel Atom SoCs) Not sure for ARM, but it may have the same problems. See also http://mjg59.dreamwidth.org/26734.html for more problems with IA32 on x86 > >> I think the solution is to restrict the build to linux-amd64, and mark >> the package as Multi-arch: foreign, however that would cover only the >> embedded EFI files, not the tools to access UEFI variables. >> That said, these tools use the efivars pseudo-filesystem and will only >> work on Linux. >> >> So, I think the next upload will restrict the package to linux-amd64 only. > > Please don't do that. There are *4* Debian Linux architectures that > should be able to work here: amd64, i386, arm64 and armhf. > I would like to, I'm just trying to find a solution that does not involved cross-compilation :/ The source package builds both native files, and .efi files. If you have any ideas they are welcome. Regards, Pierre
