[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Configure.in and SASL (ITS#536)

At 09:48 PM 5/15/00 GMT, bbense@stanford.edu wrote:
>Full_Name: Booker C. Bense
>Version: current-dev
>OS: Solaris 2.7
>URL: http://www.stanford.edu/~bbense/booker-bense-000515.patch
>Submission from: (NULL) (
>- I have built and installed cyrus sasl 1.5.20 with sleepycat DB. This requires
>that any code that uses -lsasl also use -ldb.

>A small patch to configure.in
>fixes this in my case. I'm not sure it's generally the right thing to do. 

The dependency depends on how you configure Cyrus SASL.  Cyrus SASL
can use gdbm, ndbm, or BerkeleyDB.  

>The configure.in patch is at 
>- Perhaps the right thing to do is add --with-sasl-libs 

Given that most everything is linked with SASL, LIBS would
work just as well.  However, the "real" solution is to detect
what SASL is wants, make sure it doesn't conflict with what
slapd wants, and (if necessary) add the appropriate flags.

For example, I just realized my cyrus was using the dbm interface
in FreeBSD3 libc (Berkeley DB 1.86+).  Luckily, Berkeley
DB 2.7.7 dbm interface is remapped onto other symbols.  Such
things scare me.

Of course, SASL could depend upon other libraries... most
of which we likely already pull in.