Possible bug: unable to lock memory with libgcrypt 1.7.4 on macOS Sierra 10.12.1

NIIBE Yutaka gniibe at fsij.org
Fri Dec 16 08:39:59 CET 2016

Adam Liter <io at adamliter.org> wrote:
> Hmm, I wonder if this is not necessarily a bug with libgcrypt 1.7.4 but 
> rather has something to do with how Homebrew is compiling the binary.

Thank you for your report.

I think that it is a bug of configure script in libgcrypt for the
detection if mlock function works correctly.

In libgcrypt 1.7.5, which was released yesterday, it was fixed.

More information about the Gcrypt-devel mailing list