On Oct 29 21:58, Andy Polyakov wrote: > I feel like saying few words. One should recognize that by the time > multi-threading support was taking shape there was a whole variety > of threading implementations and callbacks were the only way to > convey the specifics. Nowadays we're pretty much talking only about > pthreads and Windows, and one can indeed argue why wouldn't OpenSSL > simply default to either of the two when appropriate. While it's > more than appropriate on Windows as it is, on pthreads-powered > Unices it's not as obvious. > [...] > Ideally libcrypto should *detect* if > *hosting* application is linked with libpthread and only *then* > adjust accordingly. Is there way to detect if application is linked > with libpthread at run-time? There is DSO_global_lookup.
Please, before any change is made in terms of threading, let me point out that Cygwin is NOT Windows, even if it runs on Windows. Cygwin provides its own pthreads implementation which is always available, even without explicit linking against -lpthread. So, for Cygwin, please use pthreads, not Windows threading, otherwise applications linked against libcrypto might be broken in subtil ways. Thanks for considering, Corinna -- Corinna Vinschen Cygwin Maintainer Red Hat
pgpKeAfpitjTD.pgp
Description: PGP signature
