Building the Distribution
Once the distribution is unpacked, we’re ready to
configure it for GSSAPI support. The only option required to the
configure script to enable GSSAPI support is the enable-gssapi option, which takes one
argument: the root directory of your installed Kerberos 5
installation. Of course, additional configure options can be appended
for other authentication services that SASL supports.
Tip
Note that Cyrus SASL has several external dependencies, notably a recent vintage database library such as the Berkeley DB or GNU DBM. During build testing of Cyrus SASL on a FreeBSD host, the configure process claimed to find a compatible DB engine, yet the build failed until GDBM was installed. If you encounter build failures, ensure that you have a compatible DB library installed and have provided the appropriate configure flags so that the build system is aware of it.
For our purposes, we’ll configure with only GSSAPI support, assuming that our Kerberos 5 distribution and GSSAPI libraries have been installed in /usr/local:
% ./configure --enable-gssapi=/usr/local
Next, we’re ready to make the source distribution:
% make
Cyrus SASL is notoriously difficult to compile. Even if the configure script runs to completion, the make step may fail because of various db library mismatches or strange interactions with the Kerberos 5 distribution. Hopefully, everything compiles well, and if it does, proceed to installation and configuration:
# make install
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access