Your message dated Tue, 25 Jun 2024 18:09:56 +0200
with message-id <[email protected]>
and subject line Re: Broken gettext check in the build system of bison
has caused the Debian Bug report #923997,
regarding broken gettext check in gettext.m4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
923997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923997
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bison
Version: 2:3.0.2.dfsg-2
When building bison on a musl libc based system, creating
the package fails because it incorrectly assumes that the
libc has no gettext support.
The bison configure.ac uses
AM_GNU_GETTEXT([external], [need-ngettext])
which ends up checking for glibc internal symbols
_nl_msg_cat_cntr and _nl_domain_bindings instead of just
checking for the API in use (gettext and ngettext).
This issue is reported upstream at
http://lists.gnu.org/archive/html/bug-gettext/2015-04/msg00002.html
More discussions at the musl-libc mailing list:
http://www.openwall.com/lists/musl/2015/04/16/3
This matters for rebootstrap cross compiled build of bison,
might affect other packages too.
To fix it, remove _nl_* checks from m4/gettext.m4.
--- End Message ---
--- Begin Message ---
Version: 0.19.8.1-9
According to the author, this was fixed in 0.19.8 and later,
so I'm closing with the version in oldoldstable.
Thanks.
--- End Message ---
