configure - Configure the source tree - Apache HTTP Server Version 2.5
Modules | Directives | FAQ | Glossary | Sitemap | Report a bug Apache HTTP Server Version 2.5 Apache > HTTP Server > Documentation > Version 2.5 > Programs configure - Configure the source tree Available Languages: en | fr | ko | tr 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. Synopsis Options Environment variables See also Compiling and Installing Synopsis ¶ 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. Options ¶ Configuration options Installation directories System types Optional features Options for support programs Configuration options The following options influence the behavior of configure itself. -C --config-cache This is an alias for --cache-file=config.cache --cache-file= FILE The test results will be cached in file FILE .
This option is disabled by default. -h --help [short|recursive] Output the help and exit. With the argument short only options specific to this package will displayed. The argument recursive displays the short help of all the included packages. -n --no-create The configure script is run normally but does not create output files. This is useful to check the test results before generating makefiles for compilation. -q --quiet Do not print checking ... messages during the configure process. --srcdir= DIR Defines directory DIR to be the source file directory.
Default is the directory where configure is located, or the parent directory. --silent Same as --quiet -V --version Display copyright information and exit. Installation directories These options define the installation directory. The installation tree depends on the selected layout. --prefix= PREFIX Install architecture-independent files in PREFIX . By default the installation directory is set to /usr/local/apache2 . --exec-prefix= EPREFIX Install architecture-dependent files in EPREFIX .
By default the installation directory is set to the PREFIX directory. By 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 . Define a directory layout --enable-layout= LAYOUT Configure the source code and build scripts to assume an installation tree based on the layout LAYOUT .
This allows you to separately specify the locations for each type of file within the Apache HTTP Server installation. The config.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 . Fine tuning of the installation directories 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= DIR Install user executables in DIR . The user executables are supporting programs like htpasswd , dbmmanage , etc. which are useful for site administrators. By default DIR is set to EPREFIX /bin . --datadir= DIR Install read-only architecture-independent data in DIR . By default datadir is set to PREFIX /share .
This option is offered by autoconf and currently unused. --includedir= DIR Install C header files in DIR . By default includedir is set to EPREFIX /include . --infodir= DIR Install info documentation in DIR . By default infodir is set to PREFIX /info . This option is currently unused. --libdir= DIR Install object code libraries in DIR . By default libdir is set to EPREFIX /lib . --libexecdir= DIR Install the program executables (i.e., shared modules) in DIR .
By default libexecdir is set to EPREFIX /modules . --localstatedir= DIR Install modifiable single-machine data in DIR . By default localstatedir is set to PREFIX /var . This option is offered by autoconf and currently unused. --mandir= DIR Install the man documentation in DIR . By default mandir is set to EPREFIX /man . --oldincludedir= DIR Install C header files for non-gcc in DIR . By default oldincludedir is set to /usr/include .
This option is offered by autoconf and currently unused. --sbindir= DIR Install the system administrator executables in DIR . Those are server programs like httpd , apachectl , suexec , etc. which are necessary to run the Apache HTTP Server. By default sbindir is set to EPREFIX /bin (the same as bindir ). --sharedstatedir= DIR Install modifiable architecture-independent data in DIR . By default sharedstatedir is set to PREFIX /com .
This option is offered by autoconf and currently unused. --sysconfdir= DIR Install read-only single-machine data like the server configuration files httpd.conf , mime.types , etc. in DIR . By default sysconfdir is set to PREFIX /conf . System types 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= BUILD Defines the system type of the system on which the tools are being built.
It defaults to the result of the script config.guess . --host= HOST Defines the system type of the system on which the server will run. HOST defaults to BUILD . --target= TARGET Configure for building compilers for the system type TARGET . It defaults to HOST . This option is offered by autoconf and not necessary for the Apache HTTP Server. Optional Features These options are used to fine tune the features your HTTP server will have.
General syntax Generally you can use the following syntax to enable or disable a feature: --disable- FEATURE Do not include FEATURE . This is the same as --enable- FEATURE =no . --enable- FEATURE [= ARG ] Include FEATURE . The default value for ARG is yes . --enable- MODULE =shared The corresponding module will be built as a DSO module. By default enabled modules are linked dynamically. --enable- MODULE =static The corresponding module will be linked statically.
Note configure will not complain about --enable- foo even if foo doesn't exist, so you need to type carefully. Choosing modules to compile Most modules are compiled by default and have to be disabled explicitly or by using the keyword few (see --enable-modules , --enable-mods-shared and --enable-mods-static below for further explanation) or --enable-modules=none to be removed as a group. Other modules are not compiled by default and have to be enabled explicitly or by using the keywords all or reallyall to be available.
To find out which modules are compiled by default, run ./configure -h or ./configure --help and look under Optional Features . Suppose you are interested in mod_example1 and mod_example2 , and you see this: Optional Features: ... --disable-example1 example module 1 --enable-example2 example module 2 ... Then mod_example1 is enabled by default, and you would use --disable-example1 to not compile it. mod_example2 is disabled by default, and you would use --enable-example2 to compile it.
Multi-Processing Modules 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: --with-mpm=MPM Choose the default
The rest of this page is on the live site.