configure - Configure the source tree

script configures the source tree for compiling and installing the Apache HTTP Server on your particular platform. Various options allow the compilation of a server corresponding to your personal requirements.

This script, included in the root directory of the source distribution, is for compilation on Unix and Unix-like systems only. For other platforms, see the platform documentation.

You should call the configure

./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g. CC

. See VAR=VALUEbelow for descriptions of some of the useful variables.

The following options influence the behavior of configure

--cache-file=config.cache

only options specific to this package will displayed. The argument recursive

displays the short help of all the included packages.-n

script is run normally but does not create output files. This is useful to check the test results before generating makefiles for compilation.-q

messages during the configure process.--srcdir=DIR

is located, or the parent directory.--silent

These options define the installation directory. The installation tree depends on the selected layout.

By default, make install

will install all the files in /usr/local/apache2/bin

etc. You can specify an installation prefix other than /usr/local/apache2

, for instance --prefix=$HOME

file contains several example configurations, and you can also create your own custom configuration following the examples. The different layouts in this file are grouped into ...

sections and referred to by name as in FOO

.For better control of the installation directories, use the options below. Please note that the directory defaults are set by autoconf

and are overwritten by the corresponding layout setting.

, etc. which are useful for site administrators. By default EPREFIX/bin

and currently unused.--includedir=DIR

, etc. which are necessary to run the Apache HTTP Server. By default sbindir

.These options are used to cross-compile the Apache HTTP Server to run on another system. In normal cases, when building and running the server on the same system, these options are not used.

and not necessary for the Apache HTTP Server.These options are used to fine tune the features your HTTP server will have.

Generally you can use the following syntax to enable or disable a feature:

will not complain about --enable-foo

even if Most modules are compiled by default and have to be disabled explicitly or by using the keywords few

and --enable-mods-static

below for further explanation) to be removed.

and look under Optional Features

. Suppose you are interested in mod_example1

Optional Features: ... --disable-example1 example module 1 --enable-example2 example module 2 ...

to not compile it. mod_example2

Multi-Processing Modules, or MPMs, implement the basic behavior of the server. A single MPM must be active in order for the server to function. The list of available MPMs appears on the module index page.

MPMs can be built as DSOs for dynamic loading or statically linked with the server, and are enabled using the following options:

Choose the default MPM for your server. If MPMs are built as DSO modules (see --enable-mpms-shared

), this directive selects the MPM which will be loaded in the default configuration file. Otherwise, this directive selects the only available MPM, which will be statically linked into the server.

If this option is omitted, the default MPM for your operating system will be used.

MPM-LIST is a space-separated list of MPM names enclosed by quotation marks. For example:

--enable-mpms-shared='prefork worker'

Additionally you can use the special keyword all

, which will select all MPMs which support dynamic loading on the current platform and build them as DSO modules. For example:

To add additional third-party modules use the following options:

--with-module=module-type:module-file[, module-type:module-file]

will be searched in the module-filemodules/

subdirectory of your Apache HTTP server source tree. If it is not found there module-typeconfigure

is considering module-file to be an absolute file path and tries to copy the source file into the module-type subdirectory. If the subdirectory doesn't exist it will be created and populated with a standard Makefile.in

This option is useful to add small external modules consisting of one source file. For more complex modules you should read the vendor's documentation.

Defines a list of modules to be enabled and build as dynamic shared modules. This mean, these module have to be loaded dynamically by using the

MODULE-LIST is a space separated list of modulenames enclosed by quotation marks. The module names are given without the preceding mod_

--enable-mods-shared='headers rewrite dav'

directives for the chosen modules will be automatically generated in the main configuration file. By default, all those directives will be commented out except for the modules that are either required or explicitly selected by a configure LoadModule--enable-foo

argument. You can change the set of loaded modules by activating or deactivating the

directives in LoadModuleapache2.conf

directives for all built modules can be activated via the configure option LoadModule--enable-load-all-modules

, but will link the given modules statically. This mean, these modules will always be present while running httpd

disables the build of all modules.--enable-v4-mapped

will listen. This port number is used when generating the configuration file apache2.conf

.--with-apr-util=DIR|FILE

has been enabled configure

searches for an installed OpenSSL. You can set the directory path to the SSL/TLS toolkit instead.--with-z=DIR

library if your source configuration requires one (e.g., when mod_deflate

is enabled). You can set the directory path to the compression library instead.Several features of the Apache HTTP Server, including

use simple key/value databases for quick lookups of information. SDBM is included in the APU, so this database is always available. If you would like to use other database types, use the following options to enable them:RewriteMap

will search for the include files and libraries of a GNU DBM installation in the usual search paths. An explicit configure

for the relevant files. Finally, the --with-ndbm[=path]

, but searches for a Berkeley DB installation.The DBM options are provided by the APU and passed through to its configuration script. They are useless when using an already installed APU defined by --with-apr-util

You may use more then one DBM implementation together with your HTTP server. The appropriated DBM type will be configured within the runtime configuration at each time.

, which allows you to set uid and gid for spawned processes. suexec

are described It is possible to create a statically linked binary of a single support program by using the following options:

normally runs.--with-suexec-docroot

access is allowed for executables. Default value is --datadir/htdocs

logfile. By default the logfile is named suexec_log

together with user-specific directories (as provided by mod_userdir

. It defaults to your system settings.There are some useful environment variables to override the choices made by configure

or to help it to find libraries and programs with nonstandard names or locations.

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.4