From: Philipp Stephani <p.stephani2@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Glenn Morris <rgm@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master b99ec5d 3/3: Work around __has_attribute bug in clang 3.4
Date: Sat, 23 Jan 2021 17:32:24 +0100 [thread overview]
Message-ID: <CAArVCkTzj1kCW=rLYm8bn0HWBgVapSokJF1KfAsOAO=aUA0EZw@mail.gmail.com> (raw)
In-Reply-To: <DAE203A1-7FEB-4475-990D-A4FCA7EBCC08@acm.org>
Am Sa., 23. Jan. 2021 um 11:14 Uhr schrieb Mattias Engdegård <mattiase@acm.org>:
>
> 23 jan. 2021 kl. 01.46 skrev Paul Eggert <eggert@cs.ucla.edu>:
>
> > Perhaps someone who can build on macOS directly can provide more info about the problem. I had no problem building with clang 11.0 on Ubuntu but Apple's clang is special.
>
> Apple's clang seems to come with a builtin
>
> #define __nonnull _Nonnull
>
> which clashes with the the one in lib/cdefs.h. Perhaps we should call it something else.
Gnulib should avoid identifiers starting with an underscore, as they
are reserved for the implementation.
next prev parent reply other threads:[~2021-01-23 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210122200300.770.63187@vcs0.savannah.gnu.org>
[not found] ` <20210122200304.8BBE820A10@vcs0.savannah.gnu.org>
2021-01-22 22:49 ` master b99ec5d 3/3: Work around __has_attribute bug in clang 3.4 Glenn Morris
2021-01-23 0:46 ` Paul Eggert
2021-01-23 10:09 ` Glenn Morris
2021-01-23 10:11 ` Mattias Engdegård
2021-01-23 16:32 ` Philipp Stephani [this message]
2021-01-23 17:27 ` Eli Zaretskii
2021-01-23 19:42 ` Paul Eggert
2021-01-23 19:53 ` Doug Davis
2021-01-23 20:07 ` Mattias Engdegård
2021-01-23 20:26 ` Philipp Stephani
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='CAArVCkTzj1kCW=rLYm8bn0HWBgVapSokJF1KfAsOAO=aUA0EZw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
--cc=rgm@gnu.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).