Re: getaddrinfo module conflict

2006-07-21 Thread Alexandre Anriot
On Thu, 20 Jul 2006 08:52:30 -0700 Paul Eggert <[EMAIL PROTECTED]> wrote: > "Derek R. Price" <[EMAIL PROTECTED]> writes: > > > Yoann Vandoorselaere wrote: > >> OpenBSD is an example, but there is more, a lot of system doesn't > >> support AI_ADDRCONFIG or other specific flags, and thus would be >

Re: getaddrinfo module conflict

2006-07-20 Thread Paul Eggert
"Derek R. Price" <[EMAIL PROTECTED]> writes: > Yoann Vandoorselaere wrote: >> OpenBSD is an example, but there is more, a lot of system doesn't >> support AI_ADDRCONFIG or other specific flags, and thus would be >> affected by the same problem. > > What version of OpenBSD? I just now checked Open

Re: getaddrinfo module conflict

2006-07-20 Thread Yoann Vandoorselaere
On Thu, 2006-07-20 at 08:00 -0400, Derek R. Price wrote: > Yoann Vandoorselaere wrote: > > OpenBSD is an example, but there is more, a lot of system doesn't > > support AI_ADDRCONFIG or other specific flags, and thus would be > > affected by the same problem. > > What version of OpenBSD? The guy

Re: getaddrinfo module conflict

2006-07-20 Thread Derek R. Price
Yoann Vandoorselaere wrote: > OpenBSD is an example, but there is more, a lot of system doesn't > support AI_ADDRCONFIG or other specific flags, and thus would be > affected by the same problem. What version of OpenBSD? Regards, Derek -- Derek R. Price CVS Solutions Architect Get CVS support at

Re: getaddrinfo module conflict

2006-07-20 Thread Yoann Vandoorselaere
On Thu, 2006-07-20 at 10:17 +0200, Yoann Vandoorselaere wrote: > On Wed, 2006-07-19 at 11:43 -0400, Derek R. Price wrote: > > Yoann Vandoorselaere wrote: > > > My suggestion is that unless we can get a full featured replacement of > > > the getaddrinfo function within GnuLib (and thus replace any n

Re: getaddrinfo module conflict

2006-07-20 Thread Yoann Vandoorselaere
On Wed, 2006-07-19 at 13:39 -0400, Derek R. Price wrote: > Yoann Vandoorselaere wrote: > > There is a problem with the current version of the getaddrinfo module > > since on certain system, the getaddrinfo() function is present but > > certain flags (for example AI_ADDRCONFIG flags) are not availab

Re: getaddrinfo module conflict

2006-07-20 Thread Yoann Vandoorselaere
On Wed, 2006-07-19 at 11:43 -0400, Derek R. Price wrote: > Yoann Vandoorselaere wrote: > > My suggestion is that unless we can get a full featured replacement of > > the getaddrinfo function within GnuLib (and thus replace any non > > conforming system implementation), we should not attempt to rede

Re: getaddrinfo module conflict

2006-07-19 Thread 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,

Re: getaddrinfo module conflict

2006-07-19 Thread Simon Josefsson
> Yoann Vandoorselaere wrote: >> My suggestion is that unless we can get a full featured replacement of >> the getaddrinfo function within GnuLib (and thus replace any non >> conforming system implementation), we should not attempt to redefine any >> of the flags if the function is available on the

Re: getaddrinfo module conflict

2006-07-19 Thread Derek R. Price
Yoann Vandoorselaere wrote: > There is a problem with the current version of the getaddrinfo module > since on certain system, the getaddrinfo() function is present but > certain flags (for example AI_ADDRCONFIG flags) are not available. Yoann, could you let me know what system(s) exhibit this pro

Re: [bug-gnulib] Re: getaddrinfo module conflict

2006-07-19 Thread Derek R. Price
Bruno Haible wrote: > Derek R. Price wrote: >> +/* #define AI_PASSIVE 0x0001 /* Socket address is intended for `bind'. */ > > Some compilers warn about /* inside a comment. For this reason, I'd > recommend to use #if 0 for commenting out. > > If you really need something that looks like a comm

Re: [bug-gnulib] Re: getaddrinfo module conflict

2006-07-19 Thread Bruno Haible
Derek R. Price wrote: > +/* #define AI_PASSIVE 0x0001 /* Socket address is intended for `bind'. */ Some compilers warn about /* inside a comment. For this reason, I'd recommend to use #if 0 for commenting out. If you really need something that looks like a comment inside a comment, you can use

Re: getaddrinfo module conflict

2006-07-19 Thread Derek R. Price
Yoann Vandoorselaere wrote: > My suggestion is that unless we can get a full featured replacement of > the getaddrinfo function within GnuLib (and thus replace any non > conforming system implementation), we should not attempt to redefine any > of the flags if the function is available on the syste

getaddrinfo module conflict

2006-07-19 Thread Yoann Vandoorselaere
Hi, There is a problem with the current version of the getaddrinfo module since on certain system, the getaddrinfo() function is present but certain flags (for example AI_ADDRCONFIG flags) are not available. In this case, including the getaddrinfo.h GnuLib header will define the missing flags, bu