<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div><pre style="white-space: pre-wrap; word-wrap: break-word !important; color: #000000; font-size: 14.16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #fdfdfd;" data-mce-style="white-space: pre-wrap; word-wrap: break-word !important; color: #000000; font-size: 14.16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #fdfdfd;">I discovered that when OPENSSL_NO_SHA512 is defined, the openssl_1_0_2 stable branch build fails during the link step with unresolved symbol EVP_sha384. The attached patch fixes this issue.<br><br>peck@bay2sierra.com<br></pre></div><div data-marker="__SIG_PRE__"><div>Mobile: +1-415-420-8449<br></div><div><br data-mce-bogus="1"></div></div></div></body></html>