Apache HTTP Server Version 2.2
Apache HTTP Server Version 2.2
This document refers to the 2.2 version of Apache httpd, which is no longer maintained. The active release is documented here. If you have not already upgraded, please follow this link for more information.
You may follow this link to go to the current version of this document.
The configure 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 script from within the
root directory of the distribution.
./configure [OPTION]...
[VAR=VALUE]...
To assign environment variables (e.g. CC,
CFLAGS ...), specify them as
VAR=VALUE. See below
for descriptions of some of the useful variables.
The following options influence the behavior of
configure itself.
-C--config-cache--cache-file=config.cache--cache-file=FILE-h--help [short|recursive]short only
options specific to this package will displayed. The argument
recursive displays the short help of all the included
packages.
-n--no-createconfigure script is run normally but does
not create output files. This is useful to check the test results
before generating makefiles for compilation.-q--quietchecking ... messages during the
configure process.--srcdir=DIRconfigure is located, or
the parent directory.--silent--quietThese options define the installation directory. The installation tree depends on the selected layout.
--prefix=PREFIX/usr/local/apache2.
--exec-prefix=EPREFIXBy default, make install will install all the files in
/usr/local/apache2/bin, /usr/local/apache2/lib
etc. You can specify an installation prefix other than
/usr/local/apache2 using --prefix,
for instance --prefix=$HOME.
--enable-layout=LAYOUTconfig.layout
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 <Layout
FOO>...</Layout> sections and referred to by name as
in FOO. The default layout is Apache.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.
--bindir=DIRhtpasswd,
dbmmanage, etc. which are useful for site
administrators. By default DIR is set to
EPREFIX/bin.
--datadir=DIRdatadir is set to
PREFIX/share. This option is offered by
autoconf and currently unused.
--includedir=DIRincludedir is set to
EPREFIX/include.
--infodir=DIRinfodir is set to
PREFIX/info. This option is currently
unused.
--libdir=DIRlibdir is set to
EPREFIX/lib.
--libexecdir=DIRlibexecdir is set to
EPREFIX/modules.
--localstatedir=DIRlocalstatedir is set to
PREFIX/var. This option is offered by
autoconf and currently unused.
--mandir=DIRmandir is set to
EPREFIX/man.
--oldincludedir=DIRoldincludedir is set to
/usr/include. This option is offered by
autoconf and currently unused.
--sbindir=DIRhttpd,
apachectl, suexec, etc. which
are neccessary to run the Apache HTTP Server. By default
sbindir is set to
EPREFIX/sbin.
--sharedstatedir=DIRsharedstatedir is set to
PREFIX/com. This option is offered by
autoconf and currently unused.
--sysconfdir=DIRhttpd.conf, mime.types, etc. in
DIR. By default sysconfdir is set to
PREFIX/conf.
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.
--build=BUILDconfig.guess.
--host=HOST--target=TARGETautoconf 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:
--disable-FEATURE--enable-FEATURE=no.
--enable-FEATURE[=ARG]yes.--enable-MODULE=shared--enable-MODULE=staticconfigure will not complain about
--enable-foo even if foo doesn't
exist, so you need to type carefully.
Some modules are compiled by default and have to be disabled explicitly. Use the following options to remove discrete modules from the compilation process.
--disable-actionsmod_actions.
--disable-aliasmod_alias.--disable-asismod_asis.
--disable-auth-basicmod_auth_basic. This module provides for HTTP Basic
Authentication, where the usernames and passwords are stored in
plain text files.
--disable-autoindexmod_autoindex.
--disable-cgimod_cgi, which provides support for CGI scripts,
is enabled by default when using a non-threaded MPM. Use this
option to disable CGI support.--disable-cgidworker
support for CGI scripts is provided by
mod_cgid by default. To disable CGI support use
this option.
--disable-charset-litemod_charset_lite. This module will be installed by
default only on EBCDIC systems.
--disable-dirmod_dir.
--disable-envmod_env.--disable-httphttp
module is a basic one, enabling the server to function as an
HTTP server. It is only useful to disable it if you want to use
another protocol module instead. Don't disable this
module unless you are really sure what you are doing.
--disable-imagemapmod_imagemap.
--disable-includemod_include.
--disable-log-configmod_log_config. You won't be able to log requests
to the server without this module.
--disable-mimemod_mime associates the requested
filename's extensions with the file's behavior and content
(mime-type, language, character set and
encoding). Disabling this module is normally not recommended.--disable-negotiationmod_negotiation.
--disable-setenvifmod_setenvif.--disable-statusmod_status.
--disable-userdirmod_userdir.Some modules are compiled by default and have to be enabled
explicitly or by using the keywords most or
all (see --enable-mods-shared below for
further explanation) to be available. Therefore use the options
below.
--enable-authn-anonmod_authn_anon.
--enable-authn-dbmmod_authn_dbm provides for HTTP Basic
Authentication, where the usernames and passwords are stored in DBM
type database files. Use this option to enable the module.--enable-authz-dbmmod_authz_dbm provides for HTTP Basic
Authorization, where the usernames and groups are stored in DBM
type database files. Use this option to enable the module.--enable-auth-digestmod_auth_digest. This module uses plain text files
to store the credentials.
--enable-authnz-ldapmod_authnz_ldap.
--enable-cachemod_cache. This experimental module may be
interesting for servers with high load or caching proxy servers. At
least one storage management module (e.g.
mod_disk_cache or mod_mem_cache)
is also necessary.
--enable-cern-metamod_cern_meta.
--enable-charset-litemod_charset_lite. This module will be installed by
default only on EBCDIC systems. On other systems, you have to enable
it.
--enable-davmod_dav. Support for filesystem resources is
provided by the separate module mod_dav_fs. This
module is also automatically enabled with
--enable-dav.mod_dav can only be used together with the
http protocol module.
--enable-dav-fsmod_dav_fs. This module is a provider for the
mod_dav module, so you should also use
--enable-dav.
--enable-dav-lockmod_dav_lock which provides generic DAV
locking support for backend modules. This module needs at least
mod_dav to function, so you should also use
--enable-dav.
--enable-deflatemod_deflate.
--enable-disk-cachemod_disk_cache.
--enable-expiresExpires header control provided by
mod_expires.
--enable-ext-filtermod_ext_filter.
--enable-file-cachemod_file_cache.
--enable-headersmod_headers.
--enable-infomod_info.
--enable-ldapmod_ldap.
--enable-logiomod_logio.--enable-mem-cachemod_mem_cache.
--enable-mime-magicmod_mime_magic.
--enable-isapimod_isapi.
--enable-proxymod_proxy. The proxying capabilities for
AJP13, CONNECT, FTP,
HTTP and the balancer are provided by the separate
modules mod_proxy_ajp,
mod_proxy_connect, mod_proxy_ftp,
mod_proxy_http and
mod_proxy_balancer.
These five modules are also automatically enabled with
--enable-proxy.
--enable-proxy-ajpAJP13 (Apache JServ Protocol 1.3)
request handling, which is provided by mod_proxy_ajp.
This module is an extension for the mod_proxy module,
so you should also use --enable-proxy.--enable-proxy-balancerAJP13,
FTP and HTTP protocols, which is provided by
mod_proxy_balancer. This module is an extension for the
mod_proxy module, so you should also use
--enable-proxy.
--enable-proxy-connectCONNECT request handling,
which is provided by mod_proxy_connect. This module
is an extension for the mod_proxy module, so you
should also use --enable-proxy.--enable-proxy-ftpFTP requests, which is
provided by mod_proxy_ftp. This module
is an extension for the mod_proxy module, so you
should also use --enable-proxy.--enable-proxy-httpHTTP requests, which is
provided by mod_proxy_http. This module
is an extension for the mod_proxy module, so you
should also use --enable-proxy.--enable-rewritemod_rewrite.
--enable-somod_so. This
module will be automatically enabled if you use the
--enable-mods-shared option.
--enable-spelingmod_speling.--enable-sslmod_ssl.
--enable-unique-idmod_unique_id.--enable-usertrackmod_usertrack.
--enable-vhost-aliasmod_vhost_alias.
The following modules are useful only for developers and testing purposes and are disabled by default. Use the following options to enable them. If you are not sure whether you need one of these modules, omit them.
--enable-bucketeermod_bucketeer.
--enable-case-filtermod_case_filter.
--enable-case-filter-inmod_case_filter_in.
--enable-echomod_echo.
--enable-examplemod_example.
--enable-optional-fn-exportmod_optional_fn_export.--enable-optional-fn-importmod_optional_fn_import.--enable-optional-hook-exportmod_optional_hook_export.--enable-optional-hook-importmod_optional_hook_import.
To add the necessary Multi Processing Module and additional third-party modules use the following options:
--with-module=module-type:module-file[,
module-type:module-file]Add one or more third-party modules to the list of statically linked
modules. The module source file module-file
will be searched in the modules/module-type
subdirectory of your Apache HTTP server source tree. If it is not found
there configure 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.
apxs.
--with-mpm=MPMbeos,
mpmt_os2,
prefork, and
worker.
--enable-maintainer-mode--enable-mods-shared=MODULE-LISTDefines 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 LoadModule directive.
MODULE-LIST is a space separated list of modulenames
enclosed by quotation marks. The module names are given without the
preceding mod_. For example:
--enable-mods-shared='headers rewrite dav'
Additionally you can use the special keywords all and
most. For example,
--enable-mods-shared=most
will compile most modules and build them as DSO modules.
Caveat:
--enable-mods-shared=all does not actually build all
modules. To build all modules then, one might use:
./configure \
--with-ldap \
--enable-mods-shared="all ssl ldap cache proxy authn_alias mem_cache file_cache authnz_ldap charset_lite dav_lock disk_cache"
--enable-modules=MODULE-LIST--enable-mods-shared,
but will link the given modules statically. This mean, these modules
will always be present while running httpd. They need
not be loaded with LoadModule.--enable-v4-mapped--with-port=PORThttpd will listen.
This port number is used when generating the configuration file
httpd.conf. The default is 80.
--with-program-namehttpd.
These options are used to define optional packages.
Generally you can use the following syntax to define an optional package:
--with-PACKAGE[=ARG]yes.
--without-PACKAGE--with-PACKAGE=no. This option is provided by
autoconf but not very useful for the Apache HTTP
Server.
--with-apr=DIR|FILEconfigure the path to the
apr-config script. You may set the absolute path and name
or the directory to the installed APR. apr-config must
exist within this directory or the subdirectory
bin.
--with-apr-util=DIR|FILEconfigure the path to the
apu-config script. You may set the absolute path and name
or the directory to the installed APU. apu-config must
exist within this directory or the subdirectory
bin.
--with-ssl=DIRmod_ssl has been enabled configure
searches for an installed OpenSSL. You can set the directory path
to the SSL/TLS toolkit instead.--with-z=DIRconfigure searches automatically for an installed
zlib 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
mod_authn_dbm, mod_authz_dbm, and
mod_rewrite's DBM
RewriteMap 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:
--with-gdbm[=path]configure will
search for the include files and libraries of a GNU DBM
installation in the usual search paths. An explicit
path will cause configure to look in
path/lib and
path/include for the relevant files.
Finally, the path may specify specific include and
library paths separated by a colon.
--with-ndbm[=path]--with-gdbm, but searches for a New DBM
installation.--with-berkeley-db[=path]--with-gdbm, 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.
--enable-static-support--enable-suexecsuexec, which allows you to set
uid and gid for spawned processes. Do not use this
option unless you understand all the security implications of
running a suid binary on your server. Further options
to configure suexec are described below.It is possible to create a statically linked binary of a single support program by using the following options:
--enable-static-abab.--enable-static-checkgidcheckgid.--enable-static-htdbmhtdbm.--enable-static-htdigesthtdigest.--enable-static-htpasswdhtpasswd.--enable-static-logresolvelogresolve.--enable-static-rotatelogsrotatelogs.suexec configuration optionsThe following options are used to fine tune the behavior of suexec. See Configuring and installing suEXEC
for further information.
--with-suexec-binsuexec binary.
Default is --sbindir (see Fine tuning of installation
directories).--with-suexec-callersuexec.
It should be the same as the user under which
httpd normally runs.
--with-suexec-docrootsuexec access is allowed for executables. Default value is
--datadir/htdocs.
--with-suexec-gidminsuexec. The default value is 100.
--with-suexec-logfilesuexec logfile.
By default the logfile is named suexec_log and located in
--logfiledir.
--with-suexec-safepathPATH to
be set for processes started by suexec. Default
value is /usr/local/bin:/usr/bin:/bin.--with-suexec-userdirsuexec access
is allowed. This setting is necessary when you want to use
suexec together with user-specific directories (as
provided by mod_userdir). The default is
public_html.
--with-suexec-uidminsuexec. The default value is 100.
--with-suexec-umaskumask for processes started by
suexec. 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.
CCCFLAGSCPPCPPFLAGS-Iincludedir
if you have headers in a nonstandard directory includedir.LDFLAGS-Llibdir if you have
libraries in a nonstandard directory libdir.