On 05/12/2025 4:09 pm, Frediano Ziglio wrote: > From: Frediano Ziglio <[email protected]> > > Older binutils versions do not handle correctly PE files. > It looks like they could work if they don't produce debug information > but they mess the PE file in other way like putting invalid > flags in sections. > Also different tools will complain about the format (like > objdump and strip). > > Signed-off-by: Frediano Ziglio <[email protected]> > --- > xen/arch/x86/arch.mk | 7 ------- > 1 file changed, 7 deletions(-) > > diff --git a/xen/arch/x86/arch.mk b/xen/arch/x86/arch.mk > index 16368a498b..10eb8e4292 100644 > --- a/xen/arch/x86/arch.mk > +++ b/xen/arch/x86/arch.mk > @@ -88,13 +88,6 @@ EFI_LDFLAGS := $(patsubst -m%,-mi386pep,$(LDFLAGS)) > --subsystem=10 --enable-long > LD_PE_check_cmd = $(call ld-option,$(EFI_LDFLAGS) --image-base=0x100000000 > -o $(efi-check).efi $(efi-check).o) > XEN_BUILD_PE := $(LD_PE_check_cmd) > > -# If the above failed, it may be merely because of the linker not dealing > well > -# with debug info. Try again with stripping it. > -ifeq ($(CONFIG_DEBUG_INFO)-$(XEN_BUILD_PE),y-n) > -EFI_LDFLAGS += --strip-debug > -XEN_BUILD_PE := $(LD_PE_check_cmd) > -endif > - > ifeq ($(XEN_BUILD_PE),y) > > # Check if the linker produces fixups in PE by default
Given the practical breakage, it's clear that noone's using xen.efi generated from toolchains these old. So, while it's not completely ideal to be "dropping" xen.efi on such systems, it firmly seems like the right thing to do overall. EFI support is still available on such systems via xen.gz + MB2. Acked-by: Andrew Cooper <[email protected]>
