You can do advocacy of GNU and the GNU system in many places. But lists of
platforms in *technical documentation* are not the proper place to do so.
That is incorrect, it is an excellent place to do so. Our guidelines
also do not differentiate between technical documentation, and other
The gnulib documentation calls the GNU based systems for "glibc
platform"; I suggested that this was changed but only got unfriendly
pushback from Bruno.
The gnulib manual uses the phrase to detonate a list of operating
systems, for example
Portability problems fixed by Gnulib:
@itemize
> From: Bruno Haible
> Date: Thu, 08 Dec 2022 01:21:51 +0100
>
> Gavin Smith wrote:
> > I expect it is not a gnulib problem. install-info/install-info.c declares
> > a function called "error" which appears to clash with a function from glibc.
> > ... The "error" module is brought in by "xalloc"
This shouldn’t affect anything; it’s merely a refactoring.
* lib/verify.h (_GL_HAVE__STATIC_ASSERT1): Require
__STDC_VERSION__ to be at least 202311, instead of at least
202000. The latter number was put in in 2019 because we didn’t
yet know C23’s __STDC_VERSION__ value.
---
ChangeLog| 9
Gavin Smith wrote:
> I expect it is not a gnulib problem. install-info/install-info.c declares
> a function called "error" which appears to clash with a function from glibc.
> ... The "error" module is brought in by "xalloc" (which we
> ask for explicitly).
Yes, I think the problems already
On 12/7/22 06:53, Bruno Haible wrote:
It's pointless to do hairsplitting like this.
I tend to agree.
In situations like this, I sometimes use a handwavy phrase like "GNUish
system" or "GNU-like system". I suppose we could say something like
"present only on glibc-like platforms" but to be
On Wed, Dec 07, 2022 at 08:57:45PM +, Sam James wrote:
> ../gnulib/lib/error.h:33:13: error: type of ‘error’ does not match original
> declaration [-Werror=lto-type-mismatch]
>33 | extern void error (int __status, int __errnum, const char *__format,
> ...)
> | ^
>
Sam James writes:
> ../gnulib/lib/error.h:33:13: error: type of ‘error’ does not match original
> declaration [-Werror=lto-type-mismatch]
>33 | extern void error (int __status, int __errnum, const char *__format,
> ...)
> | ^
> install-info.c:218:1: note: type mismatch
Hi,
Compiling texinfo 7.0.1 with CFLAGS="-O2 -flto -Werror=lto-type-mismatch"
results
in the following:
```
make[3]: Entering directory
'/var/tmp/portage/sys-apps/texinfo-7.0.1/work/texinfo-7.0.1/install-info'
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../gnulib/lib
Alfred M. Szmidt wrote:
>
>Alfred M. Szmidt wrote:
>> Does a system become a `glibc platform' if one uses gnulib?
>
>No, it doesn't, because
> - the term 'platform' or 'system' denotes the basic OS + base libraries,
> - Gnulib does not emcompass glibc.
>
> Ok, so you agree
Alfred M. Szmidt wrote:
> Does a system become a `glibc platform' if one uses gnulib?
No, it doesn't, because
- the term 'platform' or 'system' denotes the basic OS + base libraries,
- Gnulib does not emcompass glibc.
Ok, so you agree that there is no such thing as a "glibc
11 matches
Mail list logo
