From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: libc-config and system-reserved symbols
Date: Sun, 29 Jan 2023 16:10:47 -0800 [thread overview]
Message-ID: <ea8b8bf6-55a5-b0c1-3309-d1be6126230f@cs.ucla.edu> (raw)
In-Reply-To: <6109082.vxZlqCtKo7@nimes>
On 2023-01-29 15:20, Bruno Haible wrote:
> Notice in particular:
> - the different definitions of __CONCAT
> - the different definitions of __inline
> - the different definitions of __always_inline
> - the different definitions of __warnattr
>
> I would not be surprised if these macros cause trouble, either on Android
> or on other platforms, in the future.
Yes, we are on thin ice here. If there is trouble I suppose we'll need
to conditionally define and use _GL_CONCAT etc. to work around it. Hope
it's not needed.
prev parent reply other threads:[~2023-01-30 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 23:06 Fix compilation errors with CC="clang -D_FORTIFY_SOURCE=2" on Android Bruno Haible
2023-01-29 23:20 ` libc-config and system-reserved symbols Bruno Haible
2023-01-30 0:10 ` Paul Eggert [this message]
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea8b8bf6-55a5-b0c1-3309-d1be6126230f@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@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.
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).