Dear Maintainer,

During a salsa-ci run of my package gem[1], blhc complained about a
missing "-Wl,-z,relro" LDFLAGS in a longish line..., only:
- the line apparently does contain "LDFLAGS=-Wl,-z,relro"
- a very similar line occuring earlier in the build output does not
  trigger the false-positive
  (that similar line is slightly shorter, as it does not contain 2 other
unrelated flags)
- the offending line is an invocation of configure (in an automake
  project), rather than a compiler invocation.

i can reproduce the problem locally by running blhc on the (attached)
file:
~~~
$ blhc gem_0.95-1+salsaci+20260706+41_amd64-2026-07-06T22_23_16Z.build
LDFLAGS missing (-Wl,-z,relro): running CONFIG_SHELL=/bin/bash /bin/bash ../../../../../extra/pix_artoolkit/configure --disable-option-checking --prefix=/usr --build=x86_64-linux-gnu --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --libdir=${exec_prefix}/lib --libexecdir=${exec_prefix}/lib --with-pd=/usr/include/pd --without-ALL --with-glfw3 --with-sdl2 --with-ftgl --with-fribidi --with-ImageMagick --with-jpeg --with-stb --with-tiff --with-lqt --with-libquicktime --with-ffmpeg --with-gmerlin_avdec --with-libmpeg3 --with-pipewire --with-libpipewire_0_3 --without-v4l --without-libv4l1 --with-v4l2 --with-libv4l2 --with-libdv --with-libdc1394_2 --with-libiec61883 --with-libraw1394 --with-unicap --with-libunicap --with-libvncclient --with-libvlc --with-DeckLink=local --with-assimp --with-build-date=on 2026/07/06 at 22:12:43 UTC --with-default-font=/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf --enable-sse2 --with-extension=linux-amd64-64.so --with-floatsize=64 --disable-plugins build_alias=x86_64-linux-gnu CXX=x86_64-linux-gnu-g++ CXXFLAGS=-g -O2 -ffile-prefix-map=/build/package/package=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection LDFLAGS=-Wl,-z,relro -Wl,-z,now CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME='""Debian/1:0.95-1+salsaci+20260706+41""' OBJCFLAGS=-g -O2 -ffile-prefix-map=/build/package/package=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection OBJCXXFLAGS=-g -O2 -ffile-prefix-map=/build/package/package=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection CC=x86_64-linux-gnu-gcc CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/package/package=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection --cache-file=/dev/null --srcdir=../../../../../extra/pix_artoolkit --no-create --no-recursion
~~~

I can work around the issue an 'ignore-line-regexp', but I wonder what is
really going on.


[1] <https://salsa.debian.org/multimedia-team/pd/gem/-/jobs/9913810>

Hi,

this is caused by the heuristic to detect if a line is a linking
command. The line with the error contains
"--with-extension=linux-amd64-64.so" which is extracted as file
extension ".so" resulting in the line being treated as linking
command. (If you want to look at the code, search for "No
compilable extensions found". $link is true and @extensions
contains ".so" for this line.)

I think the best solution in this case is ignore-line-regexp as
these cases are difficult to solve in a generic way.

Best,
Simon