2009/11/12, Constantine Sapuntzakis wrote:

> > The same way as other functions check for specific function
> > capabilities, the getaddrinfo function check now will also attempt to
> > find out if it happens to be threadsafe.
>
> Looking at your recent checkin... getaddrinfo is also probably thread
> safe if gethostbyname_r exists.
> I think it would be most straightforward HAVE_GETADDRINFO_THREADSAFE
> be defined to 1 then too.

Nope, better not go that route. Each system libraries have their own
quirks, and the configure script should not make any assumtions that
jump across functions existance and capabilities. This configure
script runs on all sorts of systems new and ancient.

Take for example systems that expose all four getaddrinfo,
gethostbyname, getaddrinfo_r and gethostbyname_r, when this happens
the non *_r functions might not be threadsafe while the *_r ones are
granted to be so.

> Also, based on my casual read of libinfo, Darwin getaddrinfo should be
> thread safe back to 10.0.

Right now the script is assuming that Darwin 9.X and later have a
threadsafe getaddrinfo. Does your comment imply that there is some
Darwin 9.X version which has a thtread-UNsafe getaddrinfo ?

If this is the case can you find out which is the first Darwin version
that has threadsafe getaddrinfo?

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html