Bug#1125774: ndpi: FTBFS on arm64: missing symbol

[Andreas Metzler]

On 2026-01-17 Adrian Bunk <bunk at debian.org> wrote:
> Control: reassign -1 libgcrypt20 1.11.2-3
> Control: affects -1 src:ndpi

> On Sat, Jan 17, 2026 at 10:20:20AM +0100, Sebastian Ramacher wrote:
> > Source: ndpi
> > Version: 4.2-2.1
> > Severity: serious
> > Tags: ftbfs
[...]
> > ndpi FTBFS on arm64:

> > https://buildd.debian.org/status/fetch.php?pkg=ndpi&arch=arm64&ver=4.2-2.1%2Bb4&stamp=1768606438&raw=0
 
> >    dh_makeshlibs -a
> > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
> > dpkg-gensymbols: warning: debian/libndpi4.2t64/DEBIAN/symbols does not match completely debian/libndpi4.2t64.symbols
> > --- debian/libndpi4.2t64.symbols (libndpi4.2t64_4.2-2.1+b4_arm64)
> > +++ dpkg-gensymbolshZBpty	2026-01-16 23:33:56.885321067 +0000
> > @@ -205,7 +205,7 @@
> >   is_diameter at Base 2.6
> >   is_udp_guessable_protocol at Base 2.6
> >   is_version_with_ietf_long_header at Base 4.0
> > - is_version_with_v1_labels at Base 4.2
> > +#MISSING: 4.2-2.1+b4# is_version_with_v1_labels at Base 4.2
> >   is_version_with_var_int_transport_params at Base 3.4
> >   jenkins_one_at_a_time_hash at Base 2.6
> >   libinjection_h5_init at Base 3.4
> > dh_makeshlibs: error: failing due to earlier errors
> > make: *** [debian/rules:19: binary-arch] Error 25

> config.log says:
> /usr/lib/gcc/aarch64-linux-gnu/15/../../../aarch64-linux-gnu/libgcrypt.so: warning: GCS is required by -z gcs, but this shared library lacks the necessary property note. The dynamic loader might not enable GCS or refuse to load the program unless all the shared library dependencies have the GCS marking.

> Related, the buildd log of libgcrypt20[1] says[2]:
> ./.libs/libgcrypt.so: warning: GCS is required by -z gcs, but this shared library lacks the necessary property note. The dynamic loader might not enable GCS or refuse to load the program unless all the shared library dependencies have the GCS marking.

> The ndpi build works with
>   export DEB_LDFLAGS_MAINT_APPEND += -Wl,-z,gcs-report-dynamic=none
> but that's obviously not desirable.
[...]

Hello,

I am too stupid to understand this. config.log says:
configure:22126: checking for gcry_cipher_checktag in -lgcrypt
configure:22155: gcc -o conftest -W -Wall -Wno-unused-parameter -Wno-unused-function -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/ametzler/NDPI/ndpi-4.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/include/json-c  -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -mbranch-protection=standard conftest.c -lgcrypt  -ljson-c  -ljson-c  >&5
/usr/lib/gcc/aarch64-linux-gnu/15/../../../aarch64-linux-gnu/libgcrypt.so: warning: GCS is required by -z gcs, but this shared library lacks the necessary property note. The dynamic loader might not enable GCS or refuse to load the program unless all the shared library dependencies have the GCS marking.
configure:22155: $? = 0
configure: failed program was:
[...]
configure:22167: result: no

However, taking the snippped "failed program" and running the quoted
"gcc -o conftest -W ..." on it yields the warning but exits
successfully. (exit code 0).

(sid/arm64 on amdahl)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'