Re: getaddrinfo module conflict

[Derek R. Price]

Simon Josefsson wrote:
> I think this is a step back, but given that the right choice seem to be to
> 1) implement support for the specific AI_ flag that was needed but missing
> here, and 2) check for availability in the system for that feature, and
> that we don't have a patch that does this now, 

Exactly.

> I won't object.  (And your
> white-space fixing patch is fine too, of course.)

Done, and done.

> I'm currently on vacation, but when I get back, I'll try to implement the
> missing flags and test the system implementation for them.  It would be
> useful to document exactly which flag(s) were needed now, and the
> workaround for it.  Yoann?

I'm not sure what workaround you are talking about, but the missing
flags are now documented in lib/getaddrinfo.h, kinda:

#if 0
/* The commented out definitions below are not yet implemented in the
   GNULIB getaddrinfo() replacement, so are not yet needed and may, in
   fact, cause conflicts on systems with a getaddrinfo() function which
   does not define them.

   If they are restored, be sure to protect the definitions
   with #ifndef.  */
#define AI_PASSIVE     0x0001  /* Socket address is intended for
                                  `bind'.  */
#define AI_NUMERICHOST 0x0004  /* Don't use name resolution.  */
#define AI_V4MAPPED    0x0008  /* IPv4 mapped addresses are
                                  acceptable.  */
#define AI_ALL         0x0010  /* Return IPv4 mapped and IPv6
                                  addresses.  */
#define AI_ADDRCONFIG  0x0020  /* Use configuration of this host to
                                  choose returned address type..  */
#endif /* 0 */


Cheers,

Derek
-- 
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 248.835.1260
f: +1 248.835.1263
<mailto:address@hidden>