From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Ping^2 Re: Fix bits/socket.h IOC* namespace issues (bug 21267)
Date: Tue, 18 Apr 2017 21:29:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1704182125210.1253@digraph.polyomino.org.uk> (raw)
In-Reply-To: <6da82597-7a9f-7990-931d-510ca2847103@linaro.org>
On Thu, 6 Apr 2017, Adhemerval Zanella wrote:
> On 05/04/2017 12:56, Joseph Myers wrote:
> > Ping^2. This patch
> > <https://sourceware.org/ml/libc-alpha/2017-03/msg00400.html> is still
> > pending review.
> >
>
> The patch itself looks good. However, I think the __SYS_SOCKET_H_undef*
> macro usage is convoluted and complex, couldn't we just copy the kernel
> definition from asm/socket.h and avoid include it on bits/socket.h?
In principle that might make sense. The issues that would need addressing
are:
* Different definitions for different architecture may well require a
separate header, much like bits/socket_type.h.
* Presumably people need to be able to include the glibc headers together
with the uapi headers, but the kernel headers define these macros
unconditionally, meaning that any difference in the text of the definition
(even keeping the same numerical value) would result in a conflict, and
care would be needed to avoid such conflicts along the lines described at
<https://sourceware.org/glibc/wiki/Synchronizing_Headers>.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-04-18 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 0:31 Joseph Myers
2017-03-23 17:59 ` Ping " Joseph Myers
2017-03-24 14:06 ` Arnd Bergmann
2017-03-27 14:46 ` Joseph Myers
2017-04-05 16:14 ` Ping^2 " Joseph Myers
2017-04-06 19:01 ` Adhemerval Zanella
2017-04-18 21:29 ` Joseph Myers [this message]
2017-04-20 19:11 ` Adhemerval Zanella
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=alpine.DEB.2.20.1704182125210.1253@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--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.
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).