On Wed, Jan 07, 2026 at 08:33:10PM -0800, Tianon Gravi wrote: > I'm sure the culprit is in > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=history;f=binutils/objcopy.c;h=ebd2a85c0f660793e91b6512c8f0adc9ea8eb9f2;hb=HEAD > somewhere, but I'm not finding it anything really obvious. 😅
>From another, similar, EFI-build-failure bug: On Mon, Jan 05, 2026 at 07:51:45PM +0100, Chris Hofstaedtler wrote: > On Mon, Jan 05, 2026 at 06:53:35PM +0100, Chris Hofstaedtler wrote: > > the following packages differ between the last good and first bad timestamp: > > binutils 2.45-8 -> 2.45.50.20251125-1 > > bisecting binutils master points to this commit: > > 5e83077d552ed6f81dbc092eb3ccf827a43de42c is the first bad commit > commit 5e83077d552ed6f81dbc092eb3ccf827a43de42c [..] > The mentioned NEWS entry says: > > * Internal changes to plugin support, and stricter target checking may result > in some errors being exposed in user options passed to the various > binutils. > For example objcopy --target=TARGET now will only work if the input file is > for TARGET whereas prior versions of objcopy accepted other target input > files and produced a TARGET output. If you do in fact want the old > behaviour the correct usage is objcopy --output-target=TARGET. https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=5e83077d552ed6f81dbc092eb3ccf827a43de42c Best, Chris
