-There are section 5 man pages for these configuration files.
-
-Building OpenLDAP For More Than One Platform
---------------------------------------------
-
-You can build OpenLDAP for more than one platform from the same source
-tree. This is accomplished by using make(1) VPATH support. If your
-make(1) program is old and doesn't have VPATH support, install BSD
-Make or GNU Make.
-
-Follow these steps for each different platform:
-
-1. Create a directory for the platform object files.
-
- % mkdir obj-platform
-
-2. Change your working directory to the platform object directory.
-
- % cd obj-platform
-
-3. Configure the build system
-
- % [env settings] ../configure --src-dir=.. [options]
-
- ( replace ".." with the appropriate path )
-
-4. Continue as above (starting at step 6).
-
-CONFIGURE OPTIONS
------------------
-
-Regrettably, this section has not been written (yet). See
-"./configure --help" for current list of options. For general
-information about how to use "configure", please read
-doc/install/configure.
-
-USING ENVIRONMENT VARIABLES
----------------------------
-
-The configure script will also use your environmental variables for
-determining compiler/linker options. This can be used to manual
-specify features and compilation options.
-
-Warning: Executables built in your environment may not run in your
-users' environments. The portability of executables between
-environments is your responsibility.
-
-Supported Environmental Variables:
-
- CC C compiler cc
- CFLAGS C flags -O -g
- CPPFLAGS cpp flags -I/path/include -Ddef
- LDFLAGS ld flags -L/usr/local/lib
- LIBS libraries -llib
- PATH command path /usr/local/bin:/usr/bin:/bin
-
-o Including alternative compilers
-
- Use the CC environment variable to tell configure to use a
- specific compiler. For example, to use GNU C Compiler instead of
- the default compiler, use:
-
- % [env] CC=gcc ./configure
-
- You can also use CC use specific flags with the specified
- compiler. For example, to require strict ANSI C using the GNU C
- Compiler, use:
-
- % [env] CC="gcc -ansi -pedantic" ./configure
-
- (you can use CFLAGS to specify compiler flags)
-
-o Preprocessor Flags
-
- You may specify additional preprocessor flags by setting
- CPPFLAGS. For example, if you would like to use headers
- installed in /usr/local/include, use:
-
- % [env] CPPFLAGS="-I/usr/local/include" ./configure
-
- You can also use CPPFLAGS to specify preprocessor macros.
-
- % [env] CPPFLAGS="-D__SPECIAL_FLAG__" ./configure
-
-o Linker Flags
-
- You may specify additional linker flags by setting LDFLAGS. For
- example, if you would like to use libraries installed in
- /usr/local/lib, use:
-
- % [env] LDFLAGS="-L/usr/local/lib" ./configure
-
- You can also use CPPFLAGS to specify linker flags:
-
- % [env] LDFLAGS="-Bstatic" ./configure
-
-o Path
-
- You may alter your path to affect configure ability to find (or
- not find) commands. For example, to have configure additionally
- look in /usr/css/bin for commands, use:
-
- % [env] PATH="/usr/css/bin:$PATH" ./configure
-
-o Using locally installed software
-
- To use software under installed under /usr/local.