On 2/6/23 18:30, Paul Eggert wrote:
1. Since the nullptr issue affects C++ so much (something I wasn't aware
of until now), I'm inclined to rename the module from c-nullptr to
nullptr as was hinted earlier. It's not just C so the "c-" is a bit
misleading.
2. The issues you mentioned about C++
Bjarni Ingi Gislason wrote:
> > ../../gnulib-tests/test-localeconv.c:53: assertion 'l->frac_digits ==
> > CHAR_MAX' failed
> > FAIL test-localeconv (exit status: 134)
> >
>
> l->frac_digits is 127 and CHAR_MAX is 255.
>
> This is due to the CFLAG "-funsigned-char"
When you connect a libc co
On Mon, Feb 06, 2023 at 01:17:29AM +, Bjarni Ingi Gislason wrote:
[...]
>
> FAIL: test-c-stack2.sh
> ==
>
> FAIL test-c-stack2.sh (exit status: 1)
>
> FAIL: test-localeconv
> =
>
> ../../gnulib-tests/test-localeconv.c:53: assertion 'l->frac_digits ==
I just found this handy script while puzzling over various problems with
help2man. In particular, it tests for cross-compilation, and copes with
help2man missing.
There are a couple of minor nits compared with direct usage of help2man,
however:
1. Before, I passed --locale=en_US.UTF-8 so I could
Paul Eggert wrote:
> It seems unlikely that a compiler would
> advertise conformance to C++11 without supporting nullptr.
Here's a case where a compiler advertises conformance to C++11 without
supporting all that's needed:
https://bugs.llvm.org/show_bug.cgi?id=44871
I'm sure there are more examp
> On 7 Feb 2023, at 12:06, Bruno Haible wrote:
>
> Thanks Paul, for reviewing what I wrote.
>
> Paul Eggert wrote:
>>> * We should stop compiling with -Wstrict-prototypes and instead (not
>>> always,
>>> but frequently enough) compile with the '-std=gnu23' option. Clang
>>> currentl
Hi Reuben,
On Feb 7 14:22, Corinna Vinschen wrote:
> On Feb 6 20:50, Reuben Thomas wrote:
> > On Mon, 6 Feb 2023 at 20:38, Bruno Haible wrote:
> >
> > > 1. 'recode' is updated to a current gnulib and publish a corresponding
> > > tarball. (Hi Reuben :) )
> > >
> >
> > I've updated gnul
Hi Bruno,
On 2/7/23 15:20, Bruno Haible wrote:
Alejandro Colomar wrote:
the last reducts of GCC defaulting to gnu89
The default standard version of GCC doesn't matter. The AC_PROG_CC macro
invocation in configure.ac arranges to add the suitable command-line options,
so that the C compiler und
Alejandro Colomar wrote:
> the last reducts of GCC defaulting to gnu89
The default standard version of GCC doesn't matter. The AC_PROG_CC macro
invocation in configure.ac arranges to add the suitable command-line options,
so that the C compiler understands C99 (or even C11 if possible).
Bruno
Hi Bruno and Branden,
On 2/7/23 15:13, Bruno Haible wrote:
G. Branden Robinson wrote:
groff's had an assert.h header
since version 1.01 (1991), but I don't know why. In 2020 I expanded it
to support C99-style assertions (i.e., assertions that communicate
meaning instead of the nearly useless f
G. Branden Robinson wrote:
> groff's had an assert.h header
> since version 1.01 (1991), but I don't know why. In 2020 I expanded it
> to support C99-style assertions (i.e., assertions that communicate
> meaning instead of the nearly useless form from C89). I am trying to
> not require C99 featur
Hi Branden,
On 2/7/23 14:43, G. Branden Robinson wrote:
[trimming and recasting subject]
Hi Alex,
At 2023-02-07T14:04:54+0100, Alejandro Colomar wrote:
I don't know if groff is supposed to be compatible with non-GNU
compilers, or if it has a dependency to GNU C compilers (GCC, Clang,
and mayb
[trimming and recasting subject]
Hi Alex,
At 2023-02-07T14:04:54+0100, Alejandro Colomar wrote:
> I don't know if groff is supposed to be compatible with non-GNU
> compilers, or if it has a dependency to GNU C compilers (GCC, Clang,
> and maybe others). If you require GNU C, maybe you should use
On Feb 6 20:50, Reuben Thomas wrote:
> On Mon, 6 Feb 2023 at 20:38, Bruno Haible wrote:
>
> > 1. 'recode' is updated to a current gnulib and publish a corresponding
> > tarball. (Hi Reuben :) )
> >
>
> I've updated gnulib in recode git; I'd be grateful if I could have a report
> that it'
Hi all,
On 2/7/23 02:06, Bruno Haible wrote:
Hi Branden,
A problem immediately arose on macOS 12.6.3. It's our good friend
vasnprintf again. Logs are available on Savannah[2].
lib/vasnprintf.c:411:16: error: expected parameter declarator
static_assert (sizeof (mp_limb_t) * CHAR_BIT == GMP_L
Bjarni Ingi Gislason wrote:
> Module LicenseFile License File name
> = == =
> LGPLv2+ LGPLv3+ or GPLv2+ lib/uniwidth/width0.h
> LGPLv2+ LGPLv3+ or GPLv2+ lib/uniwidth/width2.h
Fixed as follows. Thanks for the
Bjarni Ingi Gislason wrote:
> Module LicenseFile License File name
> = == =
> LGPLv2+ GPLlib/alignalloc.h
> LGPLv2+ GPLlib/alignalloc.c
> GPL LGPLv2+lib/glob.c
> G
Bjarni Ingi Gislason wrote:
> ./check-copyright shows in the main (master) directory:
>
> Module LicenseFile License File name
> = == =
> LGPLv2+ GPLlib/alignalloc.h
> LGPLv2+ GPLlib/a
Thanks Paul, for reviewing what I wrote.
Paul Eggert wrote:
> >* We should stop compiling with -Wstrict-prototypes and instead (not
> > always,
> > but frequently enough) compile with the '-std=gnu23' option. Clang
> > currently implements it better. GCC 13 may be on par with clang
19 matches
Mail list logo
