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

[Andreas Metzler]

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

> On Sun, Jan 18, 2026 at 07:28:22AM +0100, Andreas Metzler wrote:
> > Control: reassign 1125774 ndpi 4.2-2.1
> > 
> > On 2026-01-17 Emanuele Rocca <ema at debian.org> wrote:
[...]
> > > What's happening is that configure.ac uses AC_LANG_WERROR, which means
> > > compiler warnings are considered errors:
> > > https://sources.debian.org/src/ndpi/4.2-2.1/configure.ac#L45
> > 
> > > That's why suppressing the GCS warning fixes the build, as Adrian found.
> > 
> > Ah, thank you.
> > 
> > Let's reassign back to ndpi then.

> Why does ld complain about libgcrypt not having GCS enabled
> (as said already during the build of libgcrypt20)?

> This is the root cause, that should be fixed unless there is a good 
> reason not to do so.

> Emanuele might be better qualified to understand why this happens.

Eh.

We have
1) GCS is an optional feature. dpkg-buildflags now enables it by default
on arm64 but gcc only warns when this does not succeed.
2) libgcrypt is not yet supporting it (I suspect because there is asm in play)
3) ndpi FTBFS because of AC_LANG_WERROR.

I cannot see how this can be more than a minor or wishlist bug in
libgcrypt and a serious bug in ndpi as long as GCS is an optional
feature.[1] So 1125774 should be against ndpi.

I do not intend to play reassigning ping-pong. - Please re-assign back
if you consider my rationale convincing.

cu Andreas

[1] If it is not optional I have completely missed the announcement
and the broad testing that resulted in bugs being filed against
non-compliant packages before making it mandatory.
-- 
`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'