Readd CRYPTO_{LOCK|UNLOCK|READ|WRITE}.

These defines are part of the the locking callbacks which have been
removed. However, code that still tries to provide locking callbacks
will need these values to compile.

The locking callback that such code tries to install will be ignored,
but that's harmless since BoringSSL handles locking itself now.

Change-Id: Ic84da8b52020ccd3ecc8913b4e41d366690c7649
This commit is contained in:
Adam Langley 2015-05-27 15:46:26 -07:00
parent 71106adf89
commit 05ead68a0f

View File

@ -102,6 +102,13 @@ typedef uint32_t CRYPTO_refcount_t;
/* Deprecated functions */ /* Deprecated functions */
/* These defines do nothing but are provided to make old code easier to
* compile. */
#define CRYPTO_LOCK 1
#define CRYPTO_UNLOCK 2
#define CRYPTO_READ 4
#define CRYPTO_WRITE 8
/* CRYPTO_num_locks returns one. (This is non-zero that callers who allocate /* CRYPTO_num_locks returns one. (This is non-zero that callers who allocate
* sizeof(lock) times this value don't get zero and then fail because malloc(0) * sizeof(lock) times this value don't get zero and then fail because malloc(0)
* returned NULL.) */ * returned NULL.) */