On the 1.0.1 branch, libeay.num hasn't been updated for quite some time,
which is now resulting in a build failure on Windows. Here are the warnings
about the missing definitions:
Warning: CRYPTO_ccm128_aad does not have a number assigned
Warning: CRYPTO_ccm128_decrypt does not have a number assigned
Warning: CRYPTO_ccm128_decrypt_ccm64 does not have a number assigned
Warning: CRYPTO_ccm128_encrypt does not have a number assigned
Warning: CRYPTO_ccm128_encrypt_ccm64 does not have a number assigned
Warning: CRYPTO_ccm128_init does not have a number assigned
Warning: CRYPTO_ccm128_setiv does not have a number assigned
Warning: CRYPTO_ccm128_tag does not have a number assigned
Warning: CRYPTO_gcm128_aad does not have a number assigned
Warning: CRYPTO_gcm128_decrypt does not have a number assigned
Warning: CRYPTO_gcm128_decrypt_ctr32 does not have a number assigned
Warning: CRYPTO_gcm128_encrypt does not have a number assigned
Warning: CRYPTO_gcm128_encrypt_ctr32 does not have a number assigned
Warning: CRYPTO_gcm128_finish does not have a number assigned
Warning: CRYPTO_gcm128_init does not have a number assigned
Warning: CRYPTO_gcm128_new does not have a number assigned
Warning: CRYPTO_gcm128_release does not have a number assigned
Warning: CRYPTO_gcm128_setiv does not have a number assigned
Warning: CRYPTO_gcm128_tag does not have a number assigned
Warning: CRYPTO_nistcts128_decrypt does not have a number assigned
Warning: CRYPTO_nistcts128_decrypt_block does not have a number assigned
Warning: CRYPTO_nistcts128_encrypt does not have a number assigned
Warning: CRYPTO_nistcts128_encrypt_block does not have a number assigned
Warning: CRYPTO_xts128_encrypt does not have a number assigned
Warning: ENGINE_load_rdrand does not have a number assigned
Warning: ENGINE_load_rsax does not have a number assigned
Warning: EVP_aes_128_cbc_hmac_sha1 does not have a number assigned
Warning: EVP_aes_256_cbc_hmac_sha1 does not have a number assigned
Warning: EVP_rc4_hmac_md5 does not have a number assigned
The second- and third-from-last are now causing ssleay to fail to build,
since it uses these functions:
link /nologo /subsystem:console /opt:ref /debug /dll
/out:out32dll\ssleay32.dll /def:ms/SSLEAY32.def
@C:\Users\TyrelHa\AppData\Local\Temp\nm9F93.tmp
Creating library out32dll\ssleay32.lib and object out32dll\ssleay32.exp
ssl_algs.obj : error LNK2019: unresolved external symbol
EVP_aes_256_cbc_hmac_sha1 referenced in function SSL_library_init
ssl_algs.obj : error LNK2019: unresolved external symbol
EVP_aes_128_cbc_hmac_sha1 referenced in function SSL_library_init
out32dll\ssleay32.dll : fatal error LNK1120: 2 unresolved externals
So I just wanted to send this reminder to you. :-)
Thanks,
Tyrel
