Re: Openldap, Berkeley, Kerberos and Sasl question.

["Robert" <Robertedstrom@yahoo.com>]

"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?

> Your first problem is here.  MIT Kerberos is a fairly flawed
implementation
> right now as far as threading goes.  I suggest you get Heimdal 0.6.1 or
> later.

I will be looking at implementing hemidal.  Guess I need to head to their
website and start reading. :)

Thanks,
Robert.