I have a UEFI based motherboard: https://www.supermicro.com/products/motherboard/ATOM/X10/A1SAi-2750F.cfm and I am attempting upgrade Xen. Building is failing at a stage where binutils squawks and stops the build: efi/buildid.o: file not recognized: File format is ambiguous efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 When I built this server around December 2016, I ran into this same problem and I consulted the Xen list and learned this may be a bug in binutils. See: https://lists.xenproject.org/archives/html/xen-devel/2016-12/msg00815.html I worked around this by installing my own binutils forcing it to utilize one of the file formats above or creating my own package, I do not remember. Since I'm coming onto the problem again more than a year later, I think this may affect anyone else trying to install xen on a UEFI based system. Unfortunately, my life in the last year has been complicated and I have not been able to keep the server running, so I took it off-line. Now I am in the process of resurrecting it. I've updated everything and the only thing left to upgrade is Xen. I think this may be a bug better assigned to sys-devel/binutils-2.29.1-r1, but we'll start here. # emerge -pqv '=app-emulation/xen-4.9.1-r1::gentoo'[ebuild U ] app-emulation/xen-4.9.1-r1 [4.8.0] USE="efi flask -custom-cflags -debug" Logs to follow.
Created attachment 521396 [details] build log
Created attachment 521398 [details] emerge info
Created attachment 521400 [details] environment
*** This bug has been marked as a duplicate of bug 602052 ***
Your patch attached to #602052 still works as a workaround.
Created attachment 521790 [details] Patch for placement in /etc/portage/patches/app-emulation/xen This patch is for the /etc/portage/patches/app-emulation/xen approach to patching, whereas my previous patch in Bug #602052 was for the Portage Overlay approach.
