[patch 1/10] Don't depend on Kerberos headers when checking
librpcsecgss in configure
Neil Brown
neilb at suse.de
Mon Jul 3 20:46:57 EDT 2006
On Monday July 3, kwc at citi.umich.edu wrote:
>
> Signed-off-by: Kevin Coffman <kwc at citi.umich.edu>
>
> Older versions of MIT Kerberos are missing an OID definition, causing
> the configure checks for librpcsecgss to fail. We shouldn't be depending
> on their libraries during the configure.
>
Seems fine except...
>
> ---
>
> nfs-utils-1.0.9-pre1-kwc/configure.in | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff -puN configure.in~conf_librpcsecgss_checks configure.in
> --- nfs-utils-1.0.9-pre1/configure.in~conf_librpcsecgss_checks 2006-07-03 17:10:41.778424000 -0400
> +++ nfs-utils-1.0.9-pre1-kwc/configure.in 2006-07-03 17:10:41.812424000 -0400
> @@ -186,9 +186,9 @@ if test "$enable_gss" = yes; then
>
> dnl This is not done until here because we need to have KRBLIBS set
> dnl ("librpcsecgss=1" is so that it doesn't get added to LIBS)
> - AC_CHECK_LIB(rpcsecgss, authgss_create_default, [librpcsecgss=1], [AC_MSG_ERROR(librpcsecgss needed for nfsv4 support)], $KRBLIBS)
In my tree, this line looks like
AC_CHECK_LIB(rpcsecgss, authgss_create_default, [librpcsecgss=1], AC_MSG_ERROR([librpcsecgss needed for nfsv4 support]), $KRBLIBS)
Note the different bracketing near AC_MSG_ERROR. Obviously I could
just make the relevant change anyway, but I'm curious where that
discrepancy comes from, so I thought I would ask first.
So consider this a question (without any question-mark!!).
NeilBrown
> + AC_CHECK_LIB(rpcsecgss, authgss_create_default, [librpcsecgss=1], [AC_MSG_ERROR(librpcsecgss needed for nfsv4 support)], -lgssapi -ldl)
> AC_CHECK_LIB(rpcsecgss, authgss_set_debug_level,
> - AC_DEFINE(HAVE_AUTHGSS_SET_DEBUG_LEVEL, 1, [Define this if the rpcsec_gss library has the function authgss_set_debug_level]),, $KRBLIBS)
> + AC_DEFINE(HAVE_AUTHGSS_SET_DEBUG_LEVEL, 1, [Define this if the rpcsec_gss library has the function authgss_set_debug_level]),, -lgssapi -ldl)
>
> fi
>
>
> _
More information about the NFSv4
mailing list