[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1094244: FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’



Package: linux
Version: 6.13~rc7-1~exp1
Severity: normal
User: debian-cross@lists.debian.org
Usertags: ftcbfs

Hi,

linux 6.13~rc7-1~exp1 fails to cross build from source with build=amd64 and
host=arm64 like this:

cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -I/<<PKGBUILDDIR>>/tools/power/cpupower -I/<<PKGBUILDDIR>>/debian/build/build-tools/tools/power/cpupower -I/<<PKGBUILDDIR>>/scripts/include -isystem /<<PKGBUILDDIR>>/debian/build/build-tools/include -DVERSION=\"6.13\" -DPACKAGE=\"cpupower\" -DPACKAGE_BUGREPORT=\"Debian\ \(reportbug\ linux-cpupower\)\" -D_GNU_SOURCE -pipe -DNLS -Wall -Wchar-subscripts -Wpointer-arith -Wsign-compare -Wno-pointer-sign -Wdeclaration-after-statement -Wshadow -Os -fomit-frame-pointer -fPIC -o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/power/cpupower/lib/cpufreq.o -c lib/cpufreq.c
make[4]: *** [Makefile:193: /<<PKGBUILDDIR>>/debian/build/build-tools/tools/power/cpupower/lib/cpufreq.o] Error 1
cc: error: unrecognized command-line option ‘-mbranch-protection=standard’

This is a regression introduced by this upstream commit: f79473ed922023942407da25cb00843ac28b981c
Reverting it fixes the problem. The commit essentially replaces LD=$(CROSS)gcc
with LD?=$(CROSS)gcc so that the flags can be overridden. From the commit
message:

    pm: cpupower: Makefile: Allow overriding cross-compiling env params
    
    Allow overriding the cross-comple env parameters to make it
    easier for Yocto users. Then cross-compiler toolchains to build
    cpupower with only two steps:
    - source (toolchain path)/environment-setup-armv8a-poky-linux
    - make

I suspect that the Debian packaging can fix this by not overriding these
settings with the wrong values?

Thanks!

cheers, josch

Reply to: