Building a Gnulib testdir with a GCC 15 snapshot and "-Wall -Wextra", I see
these warnings:
../../gllib/base32.c:69:5: warning: initializer-string for array of 'char'
truncates NUL terminator but destination lacks 'nonstring' attribute (33 chars
into 32 available)
../../gllib/base64.c:63:3: warn
This patch adds a module 'dcomp-script', that supports compiling D source
code to binary from within a shell script or Makefile. Thus it's the basis
for writing D programs with the GNU Build System.
D has its own build system, called 'dub' [1], but that's overkill for
simple executables with few d
Autoconf developers: see below for a bug report on _AC_DEFINE_UNQUOTED
Gnulib developers, maybe you have an opinion on why regex.h
documentation disagrees with reality?
tl;dr: if I do add intervals to m4 regex, would you rather it be \{\}
(BRE and emacs style) or {} (ERE style)? And how to avoid
Hi Corinna,
> c) The expectations of test-file-has-acl.sh are wrong.
The Cygwin-specific part of that unit test has minimal expectations:
# Set an ACL for a group.
if setfacl -m group:0:1 tmpfile0; then
func_test_has_acl tmpfile0 yes
# Remove the ACL for t
Hi Eric,
Eric Blake wrote:
> While trying to build m4.git with clang on a Fedora 40 machine, and
> with gnulib updated to the latest git commit, I'm hitting the
> following during 'make check' (building with gcc worked):
The same build configuration (clang on Fedora 40) works for me,
except for a
While trying to build m4.git with clang on a Fedora 40 machine, and
with gnulib updated to the latest git commit, I'm hitting the
following during 'make check' (building with gcc worked):
CC test-gettimeofday.o
CCLD test-gettimeofday
/usr/bin/ld: test-gettimeofday.o: in function `mai
On 29/03/2025 16:31, Paul Eggert wrote:
On 3/29/25 04:30, Corinna Vinschen wrote:
What it should do if only the POSIX.1e draft 17 functions are available
is something along these lines:
Yes, that sounds like a better approach. However, shouldn't it use
O_PATH not O_RDONLY? We might lack read a
Eric Blake wrote:
> In gnulib/tests/init.sh, we have:
>
> # Usage: mktempd_ /tmp phoey.XX
>
> where "phooey" is a better spelling if that was the intended word, but
> where "template.XX" would read even better. Should I go ahead and
> make that change?
"phooey" appears to be a pejor
On Fri, Apr 04, 2025 at 04:54:49PM +0200, Bruno Haible wrote:
> "phooey" appears to be a pejorative word [1][2]. But there's no reason
> for negative feelings towards temporary files and directories (assuming
> that their use is safe and that they are removed after use, which a
> 'trap' command can
On Fri, Apr 04, 2025 at 09:24:35AM -0500, Eric Blake via M4-patches wrote:
> * ChangeLog-2014: Address findings from codespell.
I made this patch in response to an offline email from a contributor
who asked to remain anonymous (I find that odd in the world of open
source, but whatever), who also p
On Fri, Apr 04, 2025 at 03:33:34PM +0200, Bruno Haible wrote:
> Hi Eric,
>
> Eric Blake wrote:
> > While trying to build m4.git with clang on a Fedora 40 machine, and
> > with gnulib updated to the latest git commit, I'm hitting the
> > following during 'make check' (building with gcc worked):
>
All,
I noticed that some modern version of lcov's genhtml complain:
$ make gen-coverage PACKAGE=libtasn1-filtered
genhtml --output-directory doc/coverage \
doc/coverage/libtasn1-filtered.info \
--highlight --frames --legend \
--title "GNU Libtasn1"
genhtml: ERROR: (depreca
12 matches
Mail list logo
