On 12/09/2013 12:15 AM, Paul Eggert wrote:
> Pádraig Brady wrote:
>> * m4/gl-openssl.m4 (gl_CRYPTO_CHECK): Don't empty LIB_CRYPTO
> 
> That would inherit LIB_CRYPTO from the environment, no?
> It might be better to move the LIB_CRYPTO= into the
> initialization code.

Right, I was worried about that, hence my reluctance to push.
Where would be best to initialize this?

> Also, is libgcrypt compatible with libcrypt with
> respect to MD5, SHA512, etc.?

The libgcrypt replacement calling out to libcrypto seems to work.
tests pass anyway.

thanks,
Pádraig.


Reply via email to