From: Ondrej Valousek <webserv@s3group.cz>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: krb5 required when building with sasl support
Date: Wed, 04 Feb 2009 17:58:33 +0100 [thread overview]
Message-ID: <4989C939.7090106@s3group.cz> (raw)
In-Reply-To: <n7xy6wmw3uu.fsf@sor.suse.de>
+1 - I have spotted this, too....
O.
Matthias Koenig wrote:
> Hi,
>
> it seems that it is necessary to link also against krb5 when
> building the LDAP lookup module with SASL support.
> This is missing currently in the configure.in it only
> links with -lsasl.
> The following patch should fix this.
>
> Regards,
> Matthias
>
> Index: autofs-5.0.4/configure.in
> ===================================================================
> --- autofs-5.0.4.orig/configure.in 2008-11-04 02:36:48.000000000 +0100
> +++ autofs-5.0.4/configure.in 2009-02-04 17:30:01.000000000 +0100
> @@ -256,8 +256,13 @@ AC_ARG_WITH(sasl,
> if test -z "$HAVE_SASL" -o "$HAVE_SASL" != "0" -a "$HAVE_LIBXML" == "1"
> then
> HAVE_SASL=0
> - AC_CHECK_LIB(sasl2, sasl_client_start, HAVE_SASL=1 LIBSASL="$LIBSASL -lsasl2", , -lsasl2 $LIBS)
> + HAVE_KRB5=0
> + AC_CHECK_LIB(sasl2, sasl_client_start, HAVE_SASL=1,, -lsasl2 $LIBS)
> + AC_CHECK_LIB(krb5, krb5_mk_req_extended, HAVE_KRB5=1,, $LIBS)
> if test "$HAVE_SASL" == "1"; then
> + test "$HAVE_KRB5" != "1" && \
> + AC_MSG_FAILURE([You need krb5 libs to build with SASL support])
> + LIBSASL="$LIBSASL -lsasl2 -lkrb5"
> AC_DEFINE(WITH_SASL,1,
> [Define if using SASL authentication with the LDAP module])
> fi
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
>
next prev parent reply other threads:[~2009-02-04 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 16:42 krb5 required when building with sasl support Matthias Koenig
2009-02-04 16:58 ` Ondrej Valousek [this message]
2009-02-05 18:27 ` Guillaume Rousse
2009-02-06 11:35 ` Matthias Koenig
2009-02-06 12:23 ` Ondrej Valousek
2009-02-06 13:09 ` Guillaume Rousse
2009-02-06 13:18 ` Guillaume Rousse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4989C939.7090106@s3group.cz \
--to=webserv@s3group.cz \
--cc=autofs@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.