Many *printf implementations have bugs in the implementation of the "'" flag,
that is supposed to add thousands separators between digits.
One of these bugs became apparent when testing coreutils-9.7 across platforms.
The other one is much more insidious, and affects even relatively recent
glibc r
On Fri, Apr 11, 2025 at 04:52:59PM +0300, Vladimir Gorsunov wrote:
> When GNU Emacs switched to using gnulib for regular expression
> functionality in the etags program, some features stopped working
> (please see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=76945 for
> details). That is b
$ LC_ALL=fr_FR.UTF-8 printf "%'.50g\\n"
42351647362715016953416125033982098102569580078125,0
42 351 647 362 715 016 952 456 886 422 478 691 899 620 590 616 576
The vasnprintf code, so far, does not consider the possibility of so
many thousands separators in the %g output. This patch fixes it.
2
When GNU Emacs switched to using gnulib for regular expression
functionality in the etags program, some features stopped working
(please see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=76945 for
details). That is because RE_SYNTAX_EMACS flag combo in gnulib doesn't
have the correspondi
> strcasecmp: Support cross-compilation.
A similar error is:
checking whether newlocale with a null base works... configure: error: in
'/GNULIB/testdir-all':
configure: error: cannot run test program while cross compiling
Fixed like this:
2025-04-11 Bruno Haible
newlocale: S
On 2025-04-10 15:47, Bruno Haible wrote:
But what I could do is to change Gnulib's file-has-acl module so
that if the environment variable CYGWINLY_PEDANTIC is set,
Oh, let's not do that. We have too many environment variables already.
Thanks for explaining.
