Bug#1137421: p11-kit: FTBFS with gettext 1.0
Bruno Haible
bruno at clisp.org
Sun May 24 16:01:19 BST 2026
Hello Santiago,
> This can be probanly worked around excatly like gnutls did in
> https://gitlab.com/gnutls/gnutls/-/commit/38e5fb6613666df96cc5851ab32d4db1313ffd02
> with quoting:
> AM_GNU_GETTEXT_VERSION([0.19])
> -m4_ifdef([AM_GNU_GETTEXT_REQUIRE_VERSION],[
> +m4_ifdef([AM_GNU_GET][TEXT_REQUIRE_VERSION],[
Yes, exactly. Just like the workaround for GNU wget:
https://lists.gnu.org/archive/html/bug-wget/2025-09/msg00000.html
Alternatively, you can make the AM_GNU_GETTEXT_REQUIRE_VERSION
macro invocation unconditional. This macro was introduced in
gettext 0.19.6, in 2015. All distros nowadays, that are meant to
be used for development, ship this version or newer.
https://repology.org/project/gettext/versions
In other words, the m4_ifdef invocation was a protection against
gettext versions < 0.19.6, which are virtually nonexistent nowadays.
> but isn't this an autopoint bug?
No. The autopoint documentation states that it recognizes
AM_GNU_GETTEXT_REQUIRE_VERSION invocations with parentheses. Here
it still looks like an invocation despite the missing parentheses,
because in m4 the argument list is always optional.
autopoint does not (and will not) recognize m4_ifdef invocations;
this would be too much effort.
Bruno
More information about the Pkg-gnutls-maint
mailing list