From: Zack Weinberg <zackw@panix.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Gnulib bugs <bug-gnulib@gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
26398@debbugs.gnu.org
Subject: bug#26398: GNU LIB build fails on macOS 10.12.4
Date: Sat, 8 Apr 2017 11:24:54 -0400 [thread overview]
Message-ID: <CAKCAbMis9L+_1=JukqJT4N9AKePvUHBSttyb03pCbXSLj5gLig__41227.5404939011$1491665126$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <bdc231db-f2a9-caf6-ef8d-20f144f06702@cs.ucla.edu>
> Please try the attached patch against Emacs master.
> If it works I plan to install it into Emacs and propagate
> it into Gnulib.
This patch is incomplete. If gnulib cannot use __nonnull in
getopt_{core,ext}.h, then there is no point trying to define it in
getopt_cdefs.h. And you're going to need to put snippet/arg-nonnull
back in the module file for this to work at all, aren't you?
From glibc's point of view, I think it would be better if
getopt_core.h and getopt_ext.h simply assumed _GL_ARG_NONNULL to be
available; we can add it to either our getopt.h wrapper or to
sys/cdefs.h - I don't want to make that call unilaterally. (Do you
know of a complete list of _GL_ macros that may appear in _public_
header files?)
zw
next prev parent reply other threads:[~2017-04-08 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 7:14 bug#26398: 26.0.50; GNU LIB build fails on macOS 10.12.4 Harald Maier
2017-04-08 8:24 ` bug#26398: " Paul Eggert
2017-04-08 8:43 ` Harald Maier
2017-04-08 9:38 ` Paul Eggert
[not found] ` <bdc231db-f2a9-caf6-ef8d-20f144f06702@cs.ucla.edu>
2017-04-08 10:31 ` Harald Maier
2017-04-08 15:24 ` Zack Weinberg [this message]
[not found] ` <CAKCAbMis9L+_1=JukqJT4N9AKePvUHBSttyb03pCbXSLj5gLig@mail.gmail.com>
2017-04-09 8:03 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKCAbMis9L+_1=JukqJT4N9AKePvUHBSttyb03pCbXSLj5gLig__41227.5404939011$1491665126$gmane$org@mail.gmail.com' \
--to=zackw@panix.com \
--cc=26398@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).