Hello! I’ve been working with the libevent team trying to reconcile `_GNU_SOURCE` pollution [1] in their library, and (as was pointed out to me in a pull request [2], [3]) some errors returned by `getaddrinfo(3)` in the Linux manpage lead the end-user to think that they are available in non-`GNU_SOURCE` cases, i.e., more POSIX compliant modes, when in reality they’re not, leading to some really potentially confusing error handling [4]. While I suspect that this doesn’t affect the behavior of glibc, it most definitely affects the expectations for callers, which the man page documents. Please advise how you’d like to proceed. I will submit patches via `git format-patch` once I understand the general direction I need to implement the fix. Thank you very much! -Enji PS Apologies for the spam mtk.manpages@xxxxxxxxx; I finally read the directions in their entirety about submitting plaintext emails. 1. https://github.com/libevent/libevent/issues/460 2. https://github.com/libevent/libevent/pull/781 3. http://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/netdb.h;h=6c1af6aee1eebf32f5dcfa3bf19d7c1e7bb861d8;hb=refs/heads/master#l626 4. http://man7.org/linux/man-pages/man3/getaddrinfo.3.html
