legacy: include MD5 code in legacy provider

Reviewed-by: Ben Kaduk <kaduk@mit.edu>
(Merged from https://github.com/openssl/openssl/pull/11961)

diff --git a/crypto/md5/build.info b/crypto/md5/build.info
index afcf7c442609ca7d2fec76a8aea1536c2d9d4706..18d5342a36bfa9579de3de88d093f57e0f937a6c 100644 (file)
--- a/crypto/md5/build.info
+++ b/crypto/md5/build.info
@@ -17,11 +17,13 @@ ENDIF
 $COMMON=md5_dgst.c md5_one.c md5_sha1.c $MD5ASM
 SOURCE[../../libcrypto]=$COMMON
 SOURCE[../../providers/libimplementations.a]=$COMMON
+SOURCE[../../providers/liblegacy.a]=$COMMON
 
 # Implementations are now spread across several libraries, so the defines
 # need to be applied to all affected libraries and modules.
 DEFINE[../../libcrypto]=$MD5DEF
 DEFINE[../../providers/libimplementations.a]=$MD5DEF
+DEFINE[../../providers/liblegacy.a]=$MD5DEF
 
 GENERATE[md5-586.s]=asm/md5-586.pl