Hi Vagrant! On 1/11/22 02:10, Vagrant Cascadian wrote: > Something in the toolchain recently changed which causes u-boot arch:all > build to FTBFS... I suspect binutils, as building in "bookworm" still > works fine where binutils hasn't yet migrated. > > On arch:all builds the qemu-ppce500 target is cross-compiled. > > Full log: > > > https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=all&ver=2022.01%2Bdfsg-1&stamp=1641860624&raw=0 > > The hopefully relevent lines from the build log: > ... > {standard input}: Assembler messages: > {standard input}:127: Error: unrecognized opcode: `tlbre' > {standard input}:418: Error: unrecognized opcode: `tlbre' > {standard input}:821: Error: unrecognized opcode: `msync' > {standard input}:821: Error: unrecognized opcode: `tlbwe' > {standard input}:884: Error: unrecognized opcode: `tlbsx' > make[4]: *** [/<<PKGBUILDDIR>>/scripts/Makefile.build:253: > arch/powerpc/cpu/mpc85xx/tlb.o] Error 1 > make[3]: *** [/<<PKGBUILDDIR>>/Makefile:1810: arch/powerpc/cpu/mpc85xx] Error > 2 > make[3]: *** Waiting for unfinished jobs.... > powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost > > > If anyone has thoughts what might be the issue, please chime in!
It's most likely this upstream change [1] in binutils that broke the build. It also affects glibc [2] and the kernel [3][4], for example. Adrian > [1] > https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847 > [3] > https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=5.15.15-1&stamp=1642579068&raw=0 > [4] > https://buildd.debian.org/status/fetch.php?pkg=linux&arch=ppc64&ver=5.15.15-1&stamp=1642578946&raw=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913