From: yury Date: Fri, 6 Oct 2006 16:06:23 +0000 (+0000) Subject: - checks for CRYPTO should not be depend on GSS, capa uses crypto as well. X-Git-Tag: v1_8_0_110~486^2~673 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=6e2616b44a5f41b31b5f35db813c8b75b6129809;p=fs%2Flustre-release.git - checks for CRYPTO should not be depend on GSS, capa uses crypto as well. --- diff --git a/lustre/autoconf/lustre-core.m4 b/lustre/autoconf/lustre-core.m4 index 10edcf7..de4ac0f 100644 --- a/lustre/autoconf/lustre-core.m4 +++ b/lustre/autoconf/lustre-core.m4 @@ -680,16 +680,24 @@ if test x$enable_gss == xyes; then AC_SUBST(GSSAPI_LIBS) AC_KERBEROS_V5 +fi +]) +# +# LC_CONFIG_CRYPTO +# whether capa can be built (it needs crypto support) +# +AC_DEFUN([LC_CONFIG_CRYPTO], +[ AC_MSG_CHECKING([whether CONFIG_CRYPTO and CONFIG_CRYPTO_HMAC turned on]) if test -f $LINUX/.config && grep -q CONFIG_CRYPTO=y $LINUX/.config \ && grep -q CONFIG_CRYPTO_HMAC=y $LINUX/.config; then AC_MSG_RESULT([yes]) else AC_MSG_RESULT([no]) - AC_MSG_ERROR([Crypto support is not enabled in kernel, GSS module can't build, consider --disable-gss.]) + AC_MSG_ERROR([Crypto support is not enabled in kernel. \ +It is needed for capabilities support.]) fi -fi ]) #