On Mon, Jun 27, 2016 at 05:37:19PM +0200, Kurt Roeckx wrote: > > 1. CRYPTO_LOCK is no longer defined, apparently because some locking > > functions have been removed: > > > > - CRYPTO_num_locks() > > - CRYPTO_set_id_callback() > > - CRYPTO_set_locking_callback() > > - CRYPTO_num_locks() > > > > What API am I supposed to use instead ... and is it also available > > with previous versions of OpenSSL? > > CHANGES says: > *) OpenSSL now uses a new threading API. It is no longer necessary to > set locking callbacks to use OpenSSL in a multi-threaded environment. > There > are two supported threading models: pthreads and windows threads. It is > also possible to configure OpenSSL at compile time for "no-threads". The > old threading API should no longer be used. The functions have been > replaced with "no-op" compatibility macros. > > crypto.h seems to have: > # if OPENSSL_API_COMPAT < 0x10100000L > [...] > # define CRYPTO_num_locks() (0) > # define CRYPTO_set_locking_callback(func) > # define CRYPTO_get_locking_callback() (NULL) > # define CRYPTO_set_add_lock_callback(func) > # define CRYPTO_get_add_lock_callback() (NULL) > > I'll look into why they're inside this #if, I think that #if > should just get removed.
When I test it myself, it just works? It only fails when I actually try -DOPENSSL_API_COMPAT=0x10100000L Kurt
