Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #85288 > unrolled thread

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

Started byJohannes Schauer Marin Rodrigues <josch@debian.org>
First post2025-01-26 14:50 +0100
Last post2025-02-09 10:10 +0100
Articles 5 — 3 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1094244: FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’ Johannes Schauer Marin Rodrigues <josch@debian.org> - 2025-01-26 14:50 +0100
    Bug#1094244: FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’ Salvatore Bonaccorso <carnil@debian.org> - 2025-02-01 18:00 +0100
      Bug#1094244: FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’ Johannes Schauer Marin Rodrigues <josch@debian.org> - 2025-02-01 20:50 +0100
    Processed: Re: Bug#1094244: FTCBFS amd64 -> arm64: cc: error:  unrecognized command-line option ‘-mbranch-protection=standard’ "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-01 18:00 +0100
    Bug#1094244: marked as done (FTCBFS amd64 -> arm64: cc: error:  unrecognized command-line option ‘-mbranch-protection=standard’) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-09 10:10 +0100

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

FromJohannes Schauer Marin Rodrigues <josch@debian.org>
Date2025-01-26 14:50 +0100
SubjectBug#1094244: FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’
Message-ID<K9bbr-c1Hz-11@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#85345

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-02-01 18:00 +0100
Message-ID<Kbp0B-dAi5-3@gated-at.bofh.it>
In reply to#85288
Control: tags -1 + upstream

Hi

On Sun, Jan 26, 2025 at 02:44:44PM +0100, Johannes Schauer Marin Rodrigues wrote:
> 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?

This should be fixed upstream with 3075476a7af6 ("pm: cpupower:
Makefile: Fix cross compilation") .

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#85347

FromJohannes Schauer Marin Rodrigues <josch@debian.org>
Date2025-02-01 20:50 +0100
Message-ID<KbrF7-dCmP-1@gated-at.bofh.it>
In reply to#85345

[Multipart message — attachments visible in raw view] — view raw

Quoting Salvatore Bonaccorso (2025-02-01 17:56:36)
> This should be fixed upstream with 3075476a7af6 ("pm: cpupower: Makefile: Fix
> cross compilation") .

s/should be/is/

Thank you! :)

[toc] | [prev] | [next] | [standalone]


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

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-02-01 18:00 +0100
SubjectProcessed: Re: Bug#1094244: FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’
Message-ID<Kbp0C-dAi5-15@gated-at.bofh.it>
In reply to#85288
Processing control commands:

> tags -1 + upstream
Bug #1094244 [linux] FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’
Added tag(s) upstream.

-- 
1094244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094244
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#85442 — Bug#1094244: marked as done (FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-02-09 10:10 +0100
SubjectBug#1094244: marked as done (FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’)
Message-ID<Kebua-fv19-19@gated-at.bofh.it>
In reply to#85288

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 09 Feb 2025 09:02:08 +0000
with message-id <E1th3Ca-00AaJd-1g@fasolo.debian.org>
and subject line Bug#1094244: fixed in linux 6.13.2-1~exp1
has caused the Debian Bug report #1094244,
regarding FTCBFS amd64 -> arm64: cc: error: unrecognized command-line option ‘-mbranch-protection=standard’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1094244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094244
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web