Re: Openldap, Berkeley, Kerberos and Sasl question.

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Monday, August 09, 2004 3:39 PM -0500 Robert <Robertedstrom@yahoo.com> 
wrote:

> "Quanah Gibson-Mount" <quanah@stanford.edu> wrote in message
> AB6C721FBC4F2709D040CFE6@cadabra.stanford.edu">news:AB6C721FBC4F2709D040CFE6@cadabra.stanford.edu...
> > > env LD_RUN_PATH="/usr/local/BerkeleyDB.4.2/lib;/usr/lib2/sasl2" \
> > > LD_LIBRARY_PATH="/usr/local/BerkeleyDB.4.2/lib;/usr/lib2/sasl2" \
> >
> > These need to be seperated by ":" not ";"
>
>
> I tried using : instead of ; but still no dice.  Still get
> ./.libs/libldap.a(cyrus.o): In function `ldap_int_sasl_bind':
> /tmp/openldap-2.2.15/libraries/libldap/cyrus.c:800: undefined reference to
> `sasl_errdetail'
> /tmp/openldap-2.2.15/libraries/libldap/cyrus.c:789: undefined reference to
> `sasl_errdetail'
> /tmp/openldap-2.2.15/libraries/libldap/cyrus.c:701: undefined reference to
> `sasl_errdetail'
> collect2: ld returned 1 exit status.
>
> Should cyrus-sasl be compiled with certain flags?

Yes, you need to enable GSSAPI and specify your plugin directory.

Your LD_LIBRARY_PATH should point to the 'sasl2' directory and probably the 
'plugin' directory as well.

See:

<http://www.stanford.edu/services/directory/openldap/configuration/cyrus-sasl-build.html>

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html