Comment 11 for bug 1810274

I also tested on a 32-bit Linux virtual machine, and the behaviour is the same, objcopy fails with something like '64-bit address 0x4a2a7708000000 out of range for Intel Hex file'.

The conclusion is the same as presented before, the latest binutils have a problem when building on 32-bit machines.

For the moment, the quick workaround is to manually override the binary with one from the previous release, but this does not work for automated CI environments which use pre-packaged releases (like my xPacks).