Not to stand in the way of progress at all, but just to note we cross-compile OpenSSL libraries for an embedded linux target that is still using libc_r, not libpthread. That will not change anytime soon for us, at least on legacy systems.
Besides that, it seems much of this discussion is about native builds and config-time detection of threading support. What about cross-compiling? Kevin On Wed, Oct 30, 2013 at 7:38 PM, Nico Williams <n...@cryptonector.com>wrote: > > It's getting closer, see: > > https://github.com/nicowilliams/openssl/compare/thread_safety > > I spoke to a Linux expert and was told that the correct thing to do in > the shared build of OpenSSL is to always link with -lpthread. I assert > that this is also the correct thing to do on Solaris. It's been so for > a long time now. I.e., OpenSSL should default to using native threads > on all POSIX-like and Win32/64 systems (others will have to contribute > similar support for other environments). > > My patches nonetheless will allow apps to provide alternate threading > callbacks, just as today, except that the callbacks now may not be > changed once set, and they are set to native implementations where > possible if they are needed before they are set. > > Nico > -- > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org >
