From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org, bug-gnulib@gnu.org
Cc: Sachin Monga <smonga@linux.ibm.com>
Subject: Updating <sys/cdefs.h> in glibc and gnulib
Date: Tue, 21 Feb 2023 11:14:57 +0100 [thread overview]
Message-ID: <87ilfvqq8u.fsf@oldenburg.str.redhat.com> (raw)
Why does gnulib bundle <sys/cdefs.h>? We edit this file regularly in
glibc. In the past, some gnulib-using programs supplied their own copy
of <sys/cdefs.h> instead, even when building against glibc. This caused
build failures in the glibc headers because they (quite reasonably)
assumed that <sys/cdefs.h> defines the macros for that glibc version.
Does gnulib still override <sys/cdefs.h> unconditionally?
A version check will be difficult because sometimes, we have to backport
header fixes to older versions, and that may require adding additional
macros in <sys/cdefs.h>.
We could move glibc's internal definitions to a new header, reducing
<sys/cdefs.h> in scope, but presumably that means gnulib would just
starting bundling that other header, and we would have the same issue
once more.
Thanks,
Florian
next reply other threads:[~2023-02-21 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 10:14 Florian Weimer [this message]
2023-02-26 19:02 ` Bruno Haible
2023-02-27 14:52 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilfvqq8u.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=bug-gnulib@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=smonga@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).