From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: [alpine-devel] Non-standard C library
Date: Tue, 31 Jan 2017 14:37:41 -0500 [thread overview]
Message-ID: <20170131193741.GS1533@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170131192310.GR1533@brightrain.aerifal.cx>
On Tue, Jan 31, 2017 at 02:23:10PM -0500, Rich Felker wrote:
> On Tue, Jan 31, 2017 at 01:08:07PM -0600, A. Wilcox wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On 31/01/17 12:50, William Pitcock wrote:
> > > On Tue, Jan 31, 2017 at 12:22 PM, Harald Arnesen
> > > <harald@skogtun.org> wrote:
> > >> musl defines "IPPORT_RESERVED" in "netdb.h", while both GNU libc
> > >> and BSD libc define it in "netinet/in.h". And I can't find an
> > >> e-mail address for a musl developer without subscribing to their
> > >> mailing list.
> >
> >
> > POSIX.1-2008 clearly says IPPORT_RESERVED shall be defined in <netdb.h>:
> > http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/netdb.h.html
> >
> > .....
> >
> >
> > > I checked on both a Debian and FreeBSD machine and indeed, they
> > > both have it in netinet/in.h.
> >
> > .....
> >
> > however, POSIX.1-2008 also clearly says <netdb.h> "may also make visible
> > all symbols from <netinet/in.h>".
> >
> >
> > > What shall we do?
> >
> >
> > Theoretically, the code they are compiling is wrong; POSIX only
> > guarantees the definition in <netdb.h>. However, there is a bit of
> > leeway in the standard since <netdb.h> may include all symbols from
> > <netinet/in.h>; if it's defined there, <netdb.h> can pull that header
> > in providing the definition.
> >
> > I would say that the best thing to do in the interests of
> > compatibility would be to put the definition in <netinet/in.h> *and*
> > fix whatever broken project that is (Snobol?) to include <netdb.h>.
> > This is what FreeBSD and glibc both do; define it in <netinet/in.h>
> > and include that header in <netdb.h>.
>
> The name IPPORT_RESERVED is not reserved in the namespace for
> netinet/in.h, so it can't be added there unless it's conditional on
> nonstandard feature profile. That might be justifiable if lots of
> applications had the wrong expectation here, but being that this is
> the first time we've heard of the issue, it seems there are just a few
> (or only one) applications which are doing this wrong, and they should
> just be fixed.
I seem to have overlooked it in the second table of reserved names:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_02_02
so it does seem like we could reasonably move it to netinet/in.h.
Rich
prev parent reply other threads:[~2017-01-31 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+T2pCEB9g=un1jx0x2k+wKNQWeBt8hijEwq1Yy+qLLvb0OVrw@mail.gmail.com>
[not found] ` <20170126112655.44ad5c0e@vostro.util.wtbts.net>
[not found] ` <4EDA0683-3991-44D0-882C-C34FBD4C38B2@jirutka.cz>
[not found] ` <i2ems4.oke5ti.1hge1d6-qmf@gmx.com>
[not found] ` <CA+T2pCF+dFPhWBKcwdUSp_Fr1Jk=rT1Pweap6iPZMXjf6HFi8g@mail.gmail.com>
[not found] ` <5blaf1.okfi73.2tnq26-qmf@gmx.com>
[not found] ` <CA+T2pCErwS_KFW98fvJ86-cx-dmpruxeCVKu-gG-2Ud08UVwpw@mail.gmail.com>
[not found] ` <5890704A.8090402@mail.com>
[not found] ` <CA+T2pCHJ9-aOzd_A2=5W_eF__ja+uC4yPf6LPyOQpxJKKAreUQ@mail.gmail.com>
[not found] ` <717ca2a3-d579-4ab6-ace2-1bc0dbbb111c@skogtun.org>
2017-01-31 18:50 ` William Pitcock
2017-01-31 19:08 ` A. Wilcox
2017-01-31 19:23 ` Rich Felker
2017-01-31 19:37 ` Rich Felker [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170131193741.GS1533@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).