From Fedora Directory Server

Contents 1 Compilers 2 Tools you need 2.1 Most components and the core DS 2.2 Console and other Java components 2.3 Admin Server 2.4 Fedora Core/RHEL 2.5 Solaris 2.6 HP-UX 2.7 Windows 3 External Requirements 3.1 Introduction 3.2 Mozilla.org components 3.2.1 NSPR 3.2.2 NSS 3.2.3 SVRCORE 3.2.4 LDAPSDK 3.2.5 PerLDAP 3.3 Cyrus SASL 3.4 libicu 3.5 Net-SNMP 3.6 Berkeley DB 3.7 Fedora DS Components 4 Pulling the Directory Server Source 5 Building the Source 5.1 Notes 6 Installation

Compilers

• Linux - gcc
• Solaris - Sun Workshop compiler 6.x or higher (aka Forte C compiler - the free one works just fine)
• Windows - Visual C++ 6.0 (later versions should also work)
• HP/UX - ANSI-C compliant compiler (cc, usually found in /opt/ansic), and aC++ (aCC, usually found in /opt/aCC)

gcc may work on platforms other than Linux but it has not been tested.

Tools you need

Most components and the core DS

• Perl 5.8
• cvs 1.11+ (for checking code out of CVS - not required for building from srpm or tarball)
• GNU make 3.79.1+ ("gmake", or just "make" on Linux systems)
• GNU tar
• gzip
• zip

Console and other Java components

• java 1.4.2 or later - Must be IcedTea, or the Sun or IBM JDK - see Install_Guide for more details - GCJ 4.1 or later may be used to build, but it will not run the console
• ant 1.6.1 or later

Admin Server

• Apache 2 developer files
  • Linux - the httpd-devel and/or apr-devel packages - you need the apr-config and apxs binaries in your PATH at build time
  • Solaris - this may be /usr/local/apache2
  • HP/ux - There is a free depot web services download which includes Apache2 and Tomcat

In general, you'll need to have the compilers and tools listed above in your PATH for your operating system. The following are some OS specific settings required to be made to PATH.

Fedora Core/RHEL

No special tools are required. Most everything is included with the OS. Just make sure you have installed the programming and/or the development packages that contain cvs, gcc, make, etc.

Among the required packages are:

• db4-devel
• krb5-devel
• icu and libicu-devel
• net-snmp-devel
  • The following are needed to build the snmp ldap-agent:
  • lm_sensors-devel
  • bzip2-devel
  • zlib-devel
  • openssl-devel
  • tcp_wrappers
  • libselinux-devel
• cyrus-sasl
  • cyrus-sasl-devel
  • cyrus-sasl-gssapi is required in order to use GSSAPI/Kerberos
  • cyrus-sasl-md5 is required in order to use Digest-MD5
• pam-devel

For the console

• java (java-1.7.0-icedtea, or ibm or sun jdk 1.4.2 or later)
• ant (1.6.1 or later)

For the admin server

• httpd-devel
• apr-devel

NOTE: Fedora 8 and later uses IcedTea Java (java-1.7.0-icedtea) by default. This version can build and run the console. The java that comes by default on many other older Linux distros is GNU gcj/classpath. The Fedora DS java code cannot use this, so you will need to install the IBM or Sun JDK in order to build the java code. On RHEL, the IBM JDK is in RHEL Extras. For other distros, you will have to go to the IBM or Sun web site, download, and install it.

Solaris

Make sure /usr/ccs/bin comes first in your PATH. This directory contains some tools used by the compilers and build process (e.g. ar). Also, the Workshop compilers are usually installed in /opt/SUNWspro. An example PATH:

export PATH=/usr/ccs/bin:/opt/SUNWspro/bin:/usr/ucb:/paths/to/other/tools:/bin:/usr/bin

Make sure java, ant, apr-config, and apxs are also in your PATH.

HP-UX

The ANSI-C compiler is usually found in /opt/ansic; the HP aC++ compiler in /opt/aCC. If you also have gcc installed you may need to export CC=cc so that the configure scripts will not try to use it.

export PATH=/opt/ansic/bin:/opt/aCC/bin:/paths/to/other/tools:/bin:/and/other/system/paths

Make sure java, ant, apr-config, and apxs are also in your PATH.

Windows

The build process doesn't currently support Cygwin - we welcome help with this porting effort. MKS is required for now. Be sure to put the paths to the other tools before MKS so that the MKS versions of those programs are not used. Make sure the MSVC cl.exe and link.exe tools are in your PATH.

External Requirements

Introduction

The following external components are required to build Directory Server. In most cases, the directory server will use system components installed in e.g. /usr/lib and /usr/include. The directory server configure script will first attempt to find these components using pkg-config (e.g. pkg-config --libs nspr) or the package specific config script (e.g. icu-config or net-snmp-config). If these are not available, configure will look for these components in their standard system locations in /usr/lib and /usr/include. The directory server build now uses autotools, so you can override any and all of these paths on the configure command line. You can also build any component in a private directory and use a configure argument to tell configure to use that private component (e.g. configure --with-nspr=/usr/local). Use configure --help to list all of the available settings.

Mozilla.org components

On many platforms (RHEL5, Fedora) these components may already be provided as part of the operating system. For example, on Fedora, the package names are nspr, nss, svrcore, mozldap, and perl-Mozilla-LDAP. The first 4 also have -devel packages, and nss and mozldap have a -tools package as well.

Use the following instructions only if you need to build them from source. Each component is available from anonymous CVS from mozilla - CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot - or from source tarball.

These first 5 can be checked out into the same build tree and built as follows:

• Get the source code for NSPR (v4.6.7), NSS (v3.11.7), SVRCORE (v4.0.4), LDAPSDK (v6.0.5), and PerLDAP (1.5.2)
• Build NSPR
• Build NSS
• Build SVRCORE
• Build LDAPSDK
• Build PerLDAP

You must build the components in this order because each one depends on the previous ones in turn.

NSPR

The current version as of Jan 4 2008 is 4.6.7. The source tarball is here - ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases or to use CVS:

 cvs -z3 co -r NSPR_4_6_7_RTM mozilla/nsprpub

See http://developer.mozilla.org/en/docs/NSPR_build_instructions for build instructions.

NSS

The current version as of Jan 4 2008 is 3.11.7. The source tarball is here - ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/ or to use CVS:

 cvs -z3 co -r NSS_3_11_7_RTM mozilla/security/coreconf mozilla/security/nss mozilla/dbm mozilla/security/dbm

NSS does not currently use autotools, so there is no configure - just use make (or gmake)

• General NSS build information
• Build and install information
• Where the libs and headers go
• List of make variables you can set on the command line

SVRCORE

The current version as of Jan 4 2008 is 4.0.4. The source tarball is here - ftp://ftp.mozilla.org/pub/mozilla.org/directory/svrcore/releases/ or to use CVS:

  cvs -z3 co -r SVRCORE_4_0_4_RTM mozilla/security/svrcore

Then build it using configure and make. You will need to tell it where to find NSPR and NSS if it cannot find them automatically:

./configure [--with-nspr=/path] [--with-nss=/path]
make [USE_64=1]

Use USE_64=1 to build the 64-bit version.

LDAPSDK

The current version as of Jan 4 2008 is 6.0.5. This is also known as mozldap. The source tarball is here - ftp://ftp.mozilla.org/pub/mozilla.org/directory/c-sdk/releases/ or to use CVS:

 cvs -z3 -q co -r LDAPCSDK_6_0_5_RTM -P DirectorySDKSourceC

Then see the table below for configure and gmake arguments for your platform. Use the --enable-optimize --disable-debug configure options and BUILD_OPT=1 make flag to build an optimized build or leave them out for a debug build. You may also need to use --with-nspr=/path and --with-nss=/path to tell it where to find NSPR and NSS.

For 32 bit platforms:

 cd mozilla/directory/c-sdk; \
 ./configure --enable-clu --with-sasl --with-svrcore [--enable-optimize] [--disable-debug] && \
 make

For 64 bit platforms:

 cd mozilla/directory/c-sdk; \
 ./configure --enable-clu --with-sasl --with-svrcore --enable-64bit [--enable-optimize] [--disable-debug] && \
 make USE_64=1 [BUILD_OPT=1]

See also http://wiki.mozilla.org/LDAP_C_SDK for more information.

PerLDAP

The current version as of Jan 4 2008 is 1.5.2. The source tarball is here - ftp://ftp.mozilla.org/pub/mozilla.org/directory/perldap/releases/ or to use CVS:

 cvs -z3 co -r LDAPPERLSDK_1_5_2_RTM -P mozilla/directory/perldap

Then to build:

 cd mozilla/directory/perldap
 perl Makefile.PL
 make

See also Makefile.PL for a list of environment variables that you can use to provide paths to NSPR, NSS, and LDAPSDK libraries and include files. The built files will be created in the usual MakeMaker blib directory. There is no need to do a make install unless you want to make PerLDAP part of the perl in your operating system. This won't work unless the shared libraries for the Mozilla components above are installed in a standard location (/usr/lib or using ldconfig) or you set LD_LIBRARY_PATH before using it (which comes with its own set of headaches). You can also use the LD_RUN_PATH option to make to make perldap use the libraries in another directory at runtime.

Cyrus SASL

NOTE: Fedora DS can use the bundled version of cyrus-sasl on most linux distributions, so it's quite likely that you do not need to build Cyrus-SASL from source.

You will want version 2.1.22 or later of Cyrus SASL.

Download the source from our local directory or get tarball from upstream at ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-sasl-2.1.22.tar.gz

 gunzip -c cyrus-sasl-2.1.22.tar.gz | tar xf -
 cd cyrus-sasl-2.1.22
 export CYRUS_SASL_BUILD_PATH=`pwd`

Patches: If you are using gcc4 (i.e. Fedora Core 4) you will need to use the gcc4 patch; if you are building on HP-UX, you will need to use the HP-UX patch from our sources directory to get cyrus-sasl to compile.

Pick the configure setup for your platform listed below. Note that you will build it but you will not need to do a make install

Platform	Configure	Make	Notes
FC and RHEL	CFLAGS="-O2" ./configure [--enable-gssapi=/usr/kerberos/ (*)] --enable-static --without-des --without-openssl --without-saslauthd --prefix=$CYRUS_SASL_BUILD_PATH/built	make all install	Use CFLAGS="-g" for debug builds - will automatically build 64 bit libs on x86_64
Solaris 9 32 bit	CC="cc -O" ./configure --enable-gssapi --enable-static --without-des --without-openssl --without-saslauthd --prefix=$CYRUS_SASL_BUILD_PATH/built	make all install	Use "-g" for debug builds
Solaris 9 64 bit	CC="cc -O -xarch=v9" ./configure --enable-gssapi --enable-static --without-des --without-openssl --without-saslauthd --prefix=$CYRUS_SASL_BUILD_PATH/built	make all install	Use "-g" for debug builds
HP/UX 32 bit	CC="cc +DD32" CFLAGS="-O" ./configure --enable-gssapi --enable-static --without-des --without-openssl --without-saslauthd --prefix=$CYRUS_SASL_BUILD_PATH/built	make all install	Use -g instead of -O in CFLAGS for debug builds
HP/UX 64 bit	CC="cc +DD64" CFLAGS="-O" (**) ./configure --enable-gssapi --enable-static --without-des --without-openssl --without-saslauthd --prefix=$CYRUS_SASL_BUILD_PATH/built	make all install	Use -g instead of -O in CFLAGS for debug builds

(*) Prerequisite: krb5-devel; The package could be installed in /usr/kerberos (e.g., on RHEL 3). If your system has krb5.h in /usr/kerberos/include, please specify "--enable-gssapi=/usr/kerberos/". Otherwise, "--enable-gssapi" is set by default.
(**) If you see an error message 'ld: Unsatisfied symbol "krb5_..."', you may need to set LDFLAGS="-L/usr/lib/pa20_64/gss" or LDFLAGS="-L/usr/lib/hpux64/gss" depending upon your hardware architecture.

libicu

NOTE: Fedora DS can use the bundled version of libicu on most linux distributions, so it's quite likely that you do not need to build it from source.

libicu is also known as ICU4C or simply ICU. You need version 3.4 or later from ICU4C download . Once you have the source, please refer to the file readme.html in the source distribution for detailed information about building. For example, here are the build instructions for 3.6 - build instructions. The table below for configure and gmake arguments for your platform. Use --enable-debug for debug builds or omit it for optimized builds (the default). Note below that the --prefix requires a full path. Relative paths don't work. You may omit the --prefix argument if you want to build and install in the system locations. Version 3.4 and later

Platform	Configure	Make	Notes
FC and RHEL 32 bit	./runConfigureICU [--enable-debug] Linux --enable-64bit-libs=no --enable-rpath --disable-ustdio --prefix=$ICU_BUILD_PATH/built	make all install
FC and RHEL 64 bit	./runConfigureICU [--enable-debug] Linux --enable-64bit-libs --enable-rpath --disable-ustdio --prefix=$ICU_BUILD_PATH/built	make all install
Solaris 9 32 bit	CC=cc ./runConfigureICU [--enable-debug] Solaris --enable-64bit-libs=no --enable-rpath --disable-ustdio --prefix=$ICU_BUILD_PATH/built	gmake all install
Solaris 9 64 bit	CC=cc ./runConfigureICU [--enable-debug] Solaris --enable-64bit-libs --enable-rpath --disable-ustdio --prefix=$ICU_BUILD_PATH/built	gmake all install
HP/UX 11i 32 bit	./runConfigureICU [--enable-debug] HP-UX/ACC --enable-64bit-libs=no --enable-rpath --disable-ustdio --prefix=$ICU_BUILD_PATH/built	gmake all install
HP/UX 11i 64 bit	./runConfigureICU [--enable-debug] HP-UX/ACC --enable-64bit-libs --enable-rpath --disable-ustdio --prefix=$ICU_BUILD_PATH/built	gmake all install

Net-SNMP

NOTE: You can just use the net-snmp built in to most Linux distributions (except FC2/RHEL3 and earlier). So you probably do not need to build net-snmp from source on those platforms.

You want version 5.2.1 or later of Net-SNMP.

Get the tarball from our local sources directory or from the upstream download page. Here is a direct link to the download that should work.

In the tar command below, use GNU tar (the tar included with Solaris will not untar Net-SNMP.)

gunzip -c net-snmp-5.2.1.tar.gz | tar xf -
cd net-snmp-5.2.1
export NET_SNMP_BUILD_PATH=`pwd`

Then see the table below for configure and gmake arguments for your platform. The COMMON_ARGS for the configure command are as follows:

--with-default-snmp-version=3  --with-sys-contact="" \
--with-sys-location="" --with-logfile="" \
--with-persistent-directory=/var/net-snmp   \
--prefix="$NET_SNMP_BUILD_PATH/built" \
--disable-applications --disable-manuals \
--disable-scripts --disable-mibs

Platform	Configure	Make	Notes
FC and RHEL	CFLAGS="-O2" ./configure COMMON_ARGS	make; make install	Use CFLAGS="-g" for debug builds - automatically builds 64 bit libs on x86_64
Solaris 9 32 bit	CC=cc CFLAGS="-O2" ./configure COMMON_ARGS	gmake; gmake install	Use CFLAGS="-g" for debug builds
Solaris 9 64 bit	CC=cc CFLAGS="-O2 -xarch=v9" ./configure COMMON_ARGS	gmake; gmake install	Use -g instead of -O2 in CFLAGS for debug builds
HP/UX 11i 32 bit	CFLAGS="-O2 +DAportable" ./configure COMMON_ARGS	gmake; gmake install	Use -g instead of -O2 in CFLAGS for debug builds
HP/UX 11i 64 bit	CFLAGS="-O2 +DA2.0w +DChpux -D_LARGEFILE64_SOURCE" ./configure COMMON_ARGS	gmake; gmake install	Use -g instead of -O2 in CFLAGS for debug builds
HP/UX IA64 32 bit	CFLAGS="-O +DD32" ./configure COMMON_ARGS	gmake; gmake install	Use -g instead of -O in CFLAGS for debug builds
HP/UX IA64 64 bit	CFLAGS="-O +DD64" ./configure COMMON_ARGS	gmake; gmake install	Use -g instead of -O in CFLAGS for debug builds

Berkeley DB

NOTE: You can just use the Berkeley DB built in to most Linux distributions. So you probably do not need to build it from source on those platforms.

You need version 4.2.52 or later of sleepycat's db library. We recommend using 4.2.52 with the recommended patch sets, but you should be able to use later versions as well. You can get the source tarball and the required patches from our local sources directory or you can get the source from the download page. Here is a direct link to the source for version 4.2.52 and the patches.

untar and patch the source with the following commands (make sure you're using the GNU patch utility)

 gunzip -c db-4.2.52.NC.tar.gz | tar xf -
 cd db-4.2.52.NC
 patch -p0 < ../patch.4.2.52.1
 patch -p0 < ../patch.4.2.52.2
 patch -p0 < ../patch.4.2.52.3
 patch -p0 < ../patch.4.2.52.4
 patch -p0 < ../patch.4.2.52.5

There is an additional patch that's required on HP/UX and it's available here. If you're not using HP/UX, then you don't need this patch.

 patch -p0 < ../patch.4.2.52.hpux

After unpacking and patching the source make yourself a build directory:

mkdir built ; cd built

See the table below for the configure arguments for your platform. For debug builds on all platforms, use the --enable-debug --enable-umrw arguments instead of the --disable-debug argument to the configure command.

Platform	Configure
FC and RHEL	../dist/configure --enable-dynamic --disable-debug
Solaris 9 32 bit	CC=cc ../dist/configure --enable-dynamic --disable-debug
Solaris 9 64 bit	CC=cc CFLAGS="-xarch=v9" LDFLAGS="-xarch=v9" ../dist/configure --enable-dynamic --disable-debug
HP/UX 11i 32 bit	CC="cc -O +DAportable" ../dist/configure --enable-dynamic --disable-debug
HP/UX 11i 64 bit	CC="cc -O +DA2.0w +DChpux -D_LARGEFILE64_SOURCE" ../dist/configure --enable-dynamic --disable-debug
HP/UX IA64 32 bit	CC="cc -O2 +DD32" ../dist/configure --enable-dynamic --disable-debug
HP/UX IA64 64 bit	CC="cc -O2 +DD64" ../dist/configure --enable-dynamic --disable-debug

Build libdb.a with the following command:

make LIBDB_ARGS="libdb.a" all

The above command builds command line tools that dynamically link with the libdb shared library. While this may work, it is generally preferred to statically link the command line tools. To do so, first look at your configure line above. If it includes LDFLAGS, you'll need to include them in the build command below. If you didn't have to set LDFLAGS then you don't have to set them in LDFLAGS below, you only need to use the -static.

 rm db_archive db_checkpoint db_deadlock db_dump \
   db_load db_printlog db_recover db_stat \
   db_upgrade db_verify
 make LDFLAGS="-static $LDFLAGS" libdb.a all

Fedora DS Components

See Source for the list of source tarballs as well as CVS information (repo, tag, and module).

Pulling the Directory Server Source

See also Source to get a source tarball.

If you want to use CVS, for anonymous access, use

CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/dirsec ; export CVSROOT
cvs login

(password is empty i.e. just press Enter or Return)

If you have commit access, use

CVSROOT=:ext:yourlogin@cvs.fedoraproject.org:/cvs/dirsec ; export CVSROOT
CVS_RSH=ssh ; export CVS_RSH

You will have to apply for commit access - see our contributing page on more information on how to get CVS commit access.

OK, you're ready to pull the source. Do it!

cvs -z3 co -r RELEASETAG ldapserver

The current release tag is FedoraDirSvr110. This is a static tag.

Building the Source

The simplest way is to just do

configure [options] && make

configure attempts to find all of the dependent components using pkg-config (e.g. pkg-config --libs nspr) or using the component specific script (e.g. net-snmp-config or icu-config). If that fails, configure will attempt to use the components from the standard system locations. You can override these with either the standard configure --dir options (e.g. --libdir=/path, --includedir=/path) or by overriding specific component paths (e.g. --with-nspr=/path/to/nspr --with-nss=/path/to/nss). Use configure --help to see all of the options.

There are 3 configure options that control where the files go during the install phase:

• --with-fhs - this tells configure to use the standard FHS layout - see FHS_Packaging for details
• --with-fhs-opt - this tells configure to use the FHS /etc/opt, /var/opt, and /opt hierarchy
• --prefix=/path (default) - this is the default - the default value of prefix is /opt/dirsrv

The build honors the DESTDIR=/path option, so you could do something like

configure --with-fhs ...
make DESTDIR=/var/tmp/tmpbuild install

to copy the files under /var/tmp/tmpbuild using the FHS hierarchy - this is essentially what rpmbuild does. Developers will probably want to use something like

configure --prefix=/home/richm/fds11 && make install

to install the server under /home/rich/fds11 for testing purposes.

• USE_64=1 is for 64 bit platforms, as for all of the components that you just built.

configure [options] && make USE_64=1

Notes

I find it useful to create a build directory and run configure and make in that directory, rather than in the source directory, to keep the source directory clean (e.g. for making development tarball releases, as opposed to doing make dist).

mkdir build ; cd build
/path/to/ldapserver/configure [options] && make

This is especially useful if you are using a single source directory for building on multiple architectures:

mkdir build.f8_i386
mkdir build.f8_x86_64

and so on.

Installation

Congratulations for sticking with us this far! See our install guide on how to set up the server.