[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5890E097.1060601@adelielinux.org>
Date: Tue, 31 Jan 2017 13:08:07 -0600
From: "A. Wilcox" <awilfox@...lielinux.org>
To: musl@...ts.openwall.com
Subject: Re: Re: [alpine-devel] Non-standard C library
-----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@...gtun.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>.
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJYkOCRAAoJEMspy1GSK50Uuv4P/04VgUNWW2Dg50BNiF7zbvE8
KDEF6N781XwcwIO31+ndIRGWo0+CiHHtOHjyZ+Wspr6Zcu5/Lrpau/XAaPXHq/0B
Tu64tZxoCBuuXpyqu+fKR/wxyXDEY0YD7SRnLQc4k5QwjskAKPnt1UyvsC6pmwaW
Jy+zj91cVWlthfoFzNigprhIJ3TPCFRlZCnmnzDvK2hQZRNTR70LXpSN7ZoZjIl5
xxHVsErjMA9PWTeyFLYJ72rAwTvuFgszD9Gqo8o2WcAr8VKpdgjeoFcmC017fEHr
ajQcmpbCrEeo7stMRu7lGmoktnOnA+UAnNrTak44Eic2n6bNrK29Sa6TuB4xEg3u
3+NH/jMA8lsoMtOrdiCtLio56pU8eezP5Z4JDQE0RhKXonAF7io87FNIdJ3s6z/6
dMHXDb69hSxS60YEX1S/5djFbfXkv8PkfEsdu+e5mSTOVmFBK/FyAj52q3rrvz17
rkdYH7i0EBQJnYB2B4SKjJrgrVDBAETxue/H5sdbLFKqryMS3HPEdsJSR2Ks2Aj5
pJmdhAG3upsgMgPuyLzHcOUec3dytRIE6zo45bHgTtFuWN8031bajovp9G3Wigyj
vMDKxlNI4vwW4YQd4P5bd8ZuHzBnwvF65+AOW+yMahEzURz87X6FVm1u+xEZlV1d
gE5t9bvOnDE7+1VRtfwo
=xIKa
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
