Re: lib/dirfd.c: compiler warning: unused parameter

On Thu, May 04, 2023 at 11:30:30AM +0200, Bruno Haible wrote: > Paul Eggert wrote: > > That being said, I see a path through lib/dirfd.c where dirfd's arg is > > ignored. > > Yes, that may happen in systems that don't have d_fd nor dd_fd in 'DIR' > and are not Windows. But such systems are of the

new module 'c32swidth'

This module provides a function c32swidth(), that is like wcswidth(), except that it takes a 32-bit wide string instead of a wide string as argument. 2023-05-04 Bruno Haible c32swidth: Add tests. * tests/test-c32swidth.c: New file, based on tests/test-c32width.c. * mod

wcswidth: Fix result in case of overflow

This patch fixes a small bug in Gnulib's wcswidth replacement: When the argument string is e.g. L"xxx...xxxz\n" with a repetition of INT_MAX L'x' characters, the result has to be -1, not INT_MAX. 2023-05-04 Bruno Haible wcswidth: Fix result in case of overflow. * lib/wcswidt

c32is*, c32to*, c32width, wcswidth: Relax license

Some modules for char32_t convenience functions are currently under 'LGPLv3+ or GPLv2+' license. But I want to make the 'mbchar' module depend on them, and the 'mbchar' module is under LGPLv2+. Therefore these modules need to be under LGPLv2+ as well. I can relax the license of these module, becau

new module 'c32width'

These two patches add a function c32width(), that is like wcwidth(), except that it takes a char32_t argument instead of a wchar_t argument. 2023-05-04 Bruno Haible c32width: Add tests. * tests/test-c32width.c: New file, based on tests/test-wcwidth.c. * modules/c32widt

doc: Mention macOS wcwidth bug

macOS 12.5 has a broken wcwidth(), like NetBSD. 2023-05-04 Bruno Haible doc: Mention macOS wcwidth bug. * m4/wcwidth.m4 (gl_FUNC_WCWIDTH): Mention macOS bugs. * doc/posix-functions/wcwidth.texi: Update regarding macOS. diff --git a/doc/posix-functions/wcwidth.texi b/d

Re: FYI: disable gnulib's strtoull and strtoll tests

On Wed, May 3, 2023 at 1:34 AM Bruno Haible wrote: > Hi Jim, > ! It smells like you are using an old config.cache ? > > Or possibly there is a 'config.site' file? The configure output should > show if one is loaded. Thanks for looking, Bruno. I think you must be right about it being due to an old

Re: [PATCH] fix NFSv4 acl detection on F39

Ondrej Valousek wrote: > Well, what if we try to create a decently sized stack buffer (say 256 chars) > - in 99% we fit into that buffer (actually I can't image we would ever need > more), and if we do not fit into that buffer we just return 1 This would mean, a program behaves incorrectly just

Re: lib/dirfd.c: compiler warning: unused parameter

Paul Eggert wrote: > That being said, I see a path through lib/dirfd.c where dirfd's arg is > ignored. Yes, that may happen in systems that don't have d_fd nor dd_fd in 'DIR' and are not Windows. But such systems are of the 1980ies or 1990ies, and Gnulib does not support them any more. I would n

Re: lib/dirfd.c: compiler warning: unused parameter

Thanks, this allows analysis. What I see is: 1) The compilation command in config.log is /usr/bin/gcc-12 -o conftest -Walloc-zero -Walloca -Wall -Wextra -Wformat=2 -Wattribute-warning -Wdate-time -Wformat-security -Wfree-nonheap-object -Wimplicit-fallthrough=3 -Wmissing-noreturn -Wpedantic -Ws