On 19.11.2025 18:08, 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...
Along the lines of what Andrew said, the probing done would then want updating. Which in turn raises the need to properly know what to probe. That said, from what I've read so far it's not the building of xen.efi which would need disabling, but (as we already do for certain cases) its building with debug info included (which in turn is now going to require its stripping during the build process). Jan
