Updating in glibc and gnulib

Why does gnulib bundle ? We edit this file regularly in glibc. In the past, some gnulib-using programs supplied their own copy of instead, even when building against glibc. This caused build failures in the glibc headers because they (quite reasonably) assumed that defines the macros for that

Re: Updating in glibc and gnulib

* Bruno Haible: > Florian Weimer wrote: >> Does gnulib still override unconditionally? > > Gnulib does not override , and never did. Thanks for looking into this. gnulib's libc-config.h does this: | #ifndef __attribute_nonnull__ | /* either does not exist, or is too

[PATCH] m4: Pointer types for pthread_spinlock_init, pthread_mutex_timedlock

Without this change, these probes fail unconditionally with GCC 14 because they do not use the correct argument types. --- m4/pthread-spin.m4| 2 +- m4/pthread_mutex_timedlock.m4 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/m4/pthread-spin.m4

<    1   2