On 2022-01-11, Lennart Sorensen wrote: > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote: >> Package: u-boot >> Version: 2022.01+dfsg1-1 >> Severity: serious >> X-Debbugs-Cc: debian-powe...@lists.debian.org, q...@packages.debian.org, >> binut...@packages.debian.org >> >> 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: >> >> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/cpu/mpc85xx/.tlb.o.d -nostdinc >> -isystem /usr/lib/gcc-cross/powerpc-linux-gnu/11/include -Iinclude >> -I/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/arch/powerpc/include -include >> /<<PKGBUILDDIR>>/include/linux/kconfig.h >> -I/<<PKGBUILDDIR>>/arch/powerpc/cpu/mpc85xx -Iarch/powerpc/cpu/mpc85xx >> -D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security >> -fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing >> -fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks >> -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds >> -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized >> -fmacro-prefix-map=/<<PKGBUILDDIR>>/= -g -fstack-usage >> -Wno-format-nonliteral -Wno-address-of-packed-member >> -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned >> -D__powerpc__ -ffixed-r2 -m32 -fno-ira-hoist-pressure -Wa,-me500 >> -msoft-float -mno-string -fpic -mrelocatable -ffunction-sections >> -fdata-sections -mcall-linux -msingle-pic-base -fno-jump-tables -pipe >> -DKBUILD_BASENAME='"tlb"' -DKBUILD_MODNAME='"tlb"' -c -o >> arch/powerpc/cpu/mpc85xx/tlb.o >> /<<PKGBUILDDIR>>/arch/powerpc/cpu/mpc85xx/tlb.c >> ... >> {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! >> >> >> I could remove qemu-ppce500 from the build targets(all other targets >> build fine); I am not sure if it is used by qemu or if qemu builds all >> it's own firmwares. > > Which gcc version? I believe gcc 9 removed the code for powerpcspe > which gcc 8 deprecated. So at this point I think only llvm/clang supports > the powerpcspe targets.
gcc-11 11.2.0-13 in both the successfull (bookworm) and failing case (sid). Which is why I suspect binutils, which differs between bookworm and sid... > I don't recall if binutils also dropped support or have kept it around. The binutils versions appear to be: succeeding, bookworm 2.37-10.1 failing, sid 2.37.50.20220106-2 live well, vagrant
