cd (directory it was untarred into) ./configure make make installIf you're checking this directly out of CVS, you'll need to run "sh ./SMakefile" to build the configure script first.
Read to learn how to configure SASL. There is also a document that covers upgrade issues.
If you don't want to do this for some reason, you can set the location where the library will look for plugins by setting the environment variable SASL_PATH to the path the library should use.
You'll probably need the GNU make program, available as of this writing here.
libsasl2 can use gdbm, Berkeley db, or ndbm to implement its user/password lookup. Most systems come with ndbm these days; as of this writing, gdbm is available as this file. Berkeley DB is available from: here
For Kerberos support, you'll need the kerberos libraries. At CMU, the version we use comes from here.
For GSSAPI support you will need either MIT Kerberos 5 or the Heimdal implementation.
For OTP support you will need OPIE v2.4 and this patch.
This has been tested under Linux 2.2, Linux 2.4, Solaris 2.7 and Solaris 2.8. It should work under any platform where dynamic objects can be linked against other dynamic objects, and where the dynamic library file extension is ".so", or where libtool creates the .la files correctly.
You may want to play with your CPPFLAGS and LDFLAGS a little if you're using vendor compilers (which we recommend). You can see what compilers we use on our platforms by looking at the "SMakefile".
We've tested the latest version under Windows and are eager to see other people use it!
cd sasl\win32 copy libsasl\Release\*.dll c:\sasl-plugins copy saslANONYMOUS\Release\*.dll c:\sasl-plugins copy saslCRAM\Release\*.dll c:\sasl-plugins copy saslKERBEROSV4\Release\*.dll c:\sasl-plugins copy saslPLAIN\Release\*.dll c:\sasl-plugins
sasl\win32\cmu-sasl.reg
PATH=c:\sasl-plugins;%PATH%