Re: getaddrinfo module conflict

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: Libtool and Windows

Simon Josefsson wrote: > Please install. Thanks! Done! > (A free grammar checker that works in emacs would be useful for me...) Sorry, I don't speak emacs. :) Derek -- Derek R. Price CVS Solutions Architect Get CVS support at Ximbiot ! v: +1 248.835.1260 f: +1 248.835.126

Re: getaddrinfo module conflict

> 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: Libtool and Windows

Please install. Thanks! (A free grammar checker that works in emacs would be useful for me...) > Mind if I install the attached patch on top of this? > > 2006-07-19 Derek R. Price <[EMAIL PROTECTED]> > > * gnulib.texi (Libtool and Windows): Eliminate passive voice. > Correct gramma

Re: getaddrinfo module conflict

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

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

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

reindent lib/getaddrinfo.h

I'd like to commit this whitespace only patch on top of my last getaddrinfo.h patch. The preprocessor directive indentation was extremely inconsistent, sometimes within the same #if ... #endif sequence. 2006-07-19 Derek R. Price <[EMAIL PROTECTED]> * lib/getaddrinfo.h: Reindent & repag

Re: getaddrinfo module conflict

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

Re: Libtool and Windows

Mind if I install the attached patch on top of this? 2006-07-19 Derek R. Price <[EMAIL PROTECTED]> * gnulib.texi (Libtool and Windows): Eliminate passive voice. Correct grammar. Simon Josefsson wrote: > I installed this new section in the manual. > > /Simon > > 1.11 Libtool

getaddrinfo module conflict

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