aboutsummaryrefslogtreecommitdiff
path: root/m4/tuklib_integer.m4
diff options
context:
space:
mode:
authorLasse Collin <lasse.collin@tukaani.org>2016-03-10 20:26:49 +0200
committerLasse Collin <lasse.collin@tukaani.org>2016-06-28 21:09:46 +0300
commitd0e018016b311232e82d9a98dc68f1e3dabce794 (patch)
treedc5ccbd717ca33affcd93234d0f2cfc92dc5fb3e /m4/tuklib_integer.m4
parenttuklib_physmem: Hopefully silence a warning on Windows. (diff)
downloadxz-d0e018016b311232e82d9a98dc68f1e3dabce794.tar.xz
Build: Avoid SHA256_Init on FreeBSD and MINIX 3.
On FreeBSD 10 and older, SHA256_Init from libmd conflicts with libcrypto from OpenSSL. The OpenSSL version has different sizeof(SHA256_CTX) and it can cause weird problems if wrong SHA256_Init gets used. Looking at the source, MINIX 3 seems to have a similar issue but I'm not sure. To be safe, I disabled SHA256_Init on MINIX 3 too. NetBSD has SHA256_Init in libc and they had a similar problem, but they already fixed it in 2009. Thanks to Jim Wilcoxson for the bug report that helped in finding the problem.
Diffstat (limited to 'm4/tuklib_integer.m4')
0 files changed, 0 insertions, 0 deletions