Yoann Vandoorselaere wrote: > The getaddrinfo module in GnuLib will often result in broken application > behavior because it is really a simple replacement which fail to handle > very common getaddrinfo usage pattern. > > A common example of why it might fail is: > > if (hints && (hints->ai_flags & ~AI_CANONNAME)) > /* FIXME: Support more flags. */ > return EAI_BADFLAGS;
If you say which flags your application needs to work, maybe Simon can do something about it? > This is not right since it tend to break application that trust the > GnuLib module to provide a viable getaddrinfo replacement. I agree. If we provide a function in gnulib, it should attempt to be an as complete replacement for the standard one as possible. > What is people opinion concerning an eventual drop of the current module > to replace it by the GLIBC implementation ? Have you looked at the glibc implementation of getaddrinfo? It's impossible. There's no way to make __nss_database_lookup work in the scope of gnulib. Bruno _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib