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

[bbense@networking.stanford.edu]

On Mon, 15 May 2000, Ben Collins wrote:

> > > This is wrong. You sasl library should be linked against the libraries it
> > > needs, not require other programs to handle it. When you build libsasl,
> > > add -ldb to it, and it should work fine.
> > > 
> > 
> > - This only works if you have a shared library version of db. I
> > probably should have one, but my current configuration doesn't. 
> 
> If you don't have a shared library version, then the only way to make this
> work properly is if sasl were to use libtool (I think db2 does).

-AFAIK, cyrus-sasl does use libtool. Anyway this is what it spits at
me. 

/bin/sh ../libtool --mode=link gcc  -Wall -W -g -O2 -L/usr/local/lib
-R/usr/loca
l/lib  -o libsasl.la -rpath /usr/local/lib -version-info 8:4:1
common.lo sasluti
l.lo server.lo client.lo md5.lo dlopen.lo checkpw.lo config.lo
db_berkeley.lo -l
db -ldl -lpam -lresolv -ldb -lresolv 
mkdir .libs
 
*** Warning: This library needs some functionality provided by -ldb.
*** I have the capability to make that library automatically link in
when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
 

- It seems to me that the only way this can work is if you have
shared libraries. Linking against static libraries with the a common 
set of symbols is a classic recipe for mystery errors and spending 
alot of time down debugging ratholes. 

- Booker C. Bense