On 2025-01-04, Vagrant Cascadian wrote: > On 2024-12-22, Lucas Nussbaum wrote: >>> lib/libc/aarch64/setjmp.S: Assembler messages: >>> lib/libc/aarch64/setjmp.S:46: Warning: entity size for SHF_MERGE / >>> SHF_STRINGS not specified >>> /tmp/ccsOcV8D.s: Error: 1 warning, treating warnings as errors >>> make[2]: *** [Makefile:1496: >>> /<<PKGBUILDDIR>>/build/g12a/debug/libc/setjmp.o] Error 1 > > My hunch is this was caused by an updated binutils, based on it starting > to fail to build on 2024-12-11 in reproducible builds history: > > > https://tests.reproducible-builds.org/debian/history/arm64/arm-trusted-firmware.html > > The last successful build in sid was 2024-11-25, which probably would > have been binutils ... > [2024-11-26] Accepted binutils 2.43.50.20241126-1 (source) into > unstable (Matthias Klose) > ... > [2024-09-30] binutils 2.43.1-5 MIGRATED to testing (Debian testing watch) > [2024-09-18] Accepted binutils 2.43.1-5 (source) into unstable > (Matthias Klose) > > Will see if I can try to build with an older binutils...
Yup, building with binutils 2.43.1-5 from: deb https://snapshot.debian.org/archive/debian/20241125T204553Z/ sid main Does not trigger this problem! At least with arm-trusted-firmware 2.10.x in sid, as well as the newer 2.12.x. Not sure if this is a bug or intentional change in binutils... live well, vagrant
signature.asc
Description: PGP signature
