On 19/11/2025 5:08 pm, Marek Marczykowski-Górecki wrote: > On Wed, Nov 19, 2025 at 04:02:30PM +0000, Andrew Cooper wrote: >> Given it's now only 16.04 broken, how about simply excluding xen.efi >> with these broken toolchains? > That would mean adjusting README to say a newer binutils is required for > xen.efi, right? Then ofc we would need to figure out which version > specifically. FWIW Ubuntu 16.04 has 2.26 and Ubuntu 18.04 has 2.30. > Would raising required toolchain version (for some configuration here) > even accepted, especially if considered for backporting? > > Alternatively, simply disable building xen.efi in CI on 16.04, and maybe > document as "known issue" pointing at toolchain bug? Result is very > similar, but might be more acceptable on the process side...
xen.efi has never been part of the toolchain minimum statement. It was introduced as unconditionally enabled, with probing of the toolchain to decide whether it was capable or not. That's what XEN_BUILD_EFI is doing. ~Andrew
