Bug#1125715: diet-ng: FTBFS on arm64: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmpp57y3ut8.d -L=-z -L=relro -mbranch-protection=standard -release -wi -g -O2`
Guillem Jover <[email protected]> Fri, 16 Jan 2026 20:51:59 +0100
| Newsgroups | gmane.linux.debian.devel.dpkg.bugs |
|---|---|
| Message-ID | <aWqW3yeci5iIgTO6__3274.5581980393$1768593209$gmane$org@thunder.hadrons.org> |
Hi! On Fri, 2026-01-16 at 17:58:40 +0100, Emanuele Rocca wrote: > Control: reassign -1 dpkg-dev > Control: retitle -1 dpkg-buildflags adds branch-protection to LDFLAGS > > On 2026-01-16 04:57, Sebastian Ramacher wrote: > > ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmpp57y3ut8.d -L=-z -L=relro -mbranch-protection=standard -release -wi -g -O2` > > stdout: > > stderr: ldc2: Unknown command line argument '-mbranch-protection=standard'. Try: 'ldc2 --help' > > ldc2: Did you mean '--fcf-protection=standard'? > > It seems that dpkg-buildflags erroneously started adding to LDFLAGS > -mbranch-protection=standard, while that is not a linker argument. Hmm, according to #1115292 (commit cdf5f5da0e0cb6f9f4d51e93fd9583bd578c252f) this is needed to avoid warnings from the compiler. Was that analysis wrong somehow? At this point all options seem pretty bad to me. :/ Thanks, Guillem