2022年01月23日 21:48
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 asVAR=VALUE. Seebelowfor descriptions of some of the useful variables.
The following options influence the behavior of configure itself.This is an alias for --cache-file=config.cacheThe test results will be cached in file FILE. This option is disabled by default.
Output the help and exit. With the argumentshortonly options specific to this package will displayed. The argumentrecursivedisplays the short help of all the included packages.
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.Do not print checking ... messages during the configure process.Defines directory DIR to be the source file directory. Default is the directory where configure is located, or the parent directory.Same as --quietDisplay copyright information and exit.
These options define the installation directory. The installation tree depends on the selected layout.
Install architecture-independent files in PREFIX. By default the installation directory is set to /usr/local/apache2.Install architecture-dependent files in EPREFIX. By default the installation directory is set to the PREFIX directory.
By default,make installwill install all the files in/usr/local/apache2/bin,/usr/local/apache2/libetc. You can specify an installation prefix other than/usr/local/apache2using--prefix, for instance--prefix=$HOME.
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. Theconfig.layoutfile 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 isApache.
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.Install user executables in DIR. The user executables are supporting programs likehtpasswd,dbmmanage, etc. which are useful for site administrators. By default DIR is set toEPREFIX/bin.
Install read-only architecture-independent data in DIR. By defaultdatadiris set toPREFIX/share. This option is offered byautoconfand currently unused.
Install C header files in DIR. By defaultincludediris set toEPREFIX/include.
Install info documentation in DIR. By defaultinfodiris set toPREFIX/info. This option is currently unused.
Install object code libraries in DIR. By default libdir is set to EPREFIX/lib.Install the program executables (i.e., shared modules) in DIR. By defaultlibexecdiris set toEPREFIX/modules.
Install modifiable single-machine data in DIR. By defaultlocalstatediris set toPREFIX/var. This option is offered byautoconfand currently unused.
Install the man documentation in DIR. By defaultmandiris set toEPREFIX/man.
Install C header files for non-gcc in DIR. By defaultoldincludediris set to/usr/include. This option is offered byautoconfand currently unused.
Install the system administrator executables in DIR. Those are server programs likehttpd,apachectl,suexec, etc. which are necessary to run the Apache HTTP Server. By defaultsbindiris set toEPREFIX/sbin.
Install modifiable architecture-independent data in DIR. By defaultsharedstatediris set toPREFIX/com. This option is offered byautoconfand currently unused.
Install read-only single-machine data like the server configuration fileshttpd.conf,mime.types, etc. in DIR. By defaultsysconfdiris set toPREFIX/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.
Defines the system type of the system on which the tools are being built. It defaults to the result of the script config.guess.Defines the system type of the system on which the server will run. HOST defaults to BUILD.
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.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:
Do not include FEATURE. This is the same as --enable-FEATURE=no.Include FEATURE. The default value for ARG is yes.The corresponding module will be built as a DSO module. By default enabled modules are linked dynamically.
The corresponding module will be linked statically.
Note
configurewill not complain about--enable-fooeven iffoodoesn't exist, so you need to type carefully.
Most modules are compiled by default and have to be disabled explicitly or by using the keywordfew(see--enable-modules,--enable-mods-sharedand--enable-mods-staticbelow for further explanation) or--enable-modules=noneto be removed as a group.
Other modules are not compiled by default and have to be enabled explicitly or by using the keywordsallorreallyallto be available.
To find out which modules are compiled by default, run./configure -hor./configure --helpand look underOptional Features. Suppose you are interested inmod_example1andmod_example2, and you see this:
Optional Features:
...
--disable-example1 example module1
--enable-example2 example module2
...
Thenmod_example1is enabled by default, and you would use--disable-example1to not compile it.mod_example2is disabled by default, and you would use--enable-example2to compile it.
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 themodule 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.Enable a list of MPMs as dynamic shared modules. One of these modules must be loaded dynamically using the LoadModule directive.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:
--enable-mpms-shared=all
To add additional third-party modules use the following options:
Add one or more third-party modules to the list of statically linked modules. The module source filemodule-filewill be searched in themodules/module-typesubdirectory of your Apache HTTP server source tree. If it is not found thereconfigureis 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 standardMakefile.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.
NOTE
If you want to build a DSO module instead of a statically linked useapxs.
ノート
もしあなたがスタティックなリンクの代わりに DSO モジュールをビルドしたい場合は apxs を使ってください.
Turn on debugging and compile time warnings and load all compiled modules.
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 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 keywordsreallyall,all,mostandfew. For example,
--enable-modes-shared=most
will compile most modules and build them as DSO modules,
--enable-modes-shared=few
will only compile a very basic set of modules.
The default set is most.TheLoadModuledirectives 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--enable-fooargument. You can change the set of loaded modules by activating or deactivating theLoadModuledirectives in httpd.conf. In addition theLoadModuledirectives for all built modules can be activated via the configure option--enable-load-all-modules.
This option behaves similar to--enable-mods-shared, but will link the given modules statically. This mean, these modules will always be present while runninghttpd. They need not be loaded withLoadModule.
This option behaves like to--enable-mods-shared, and will also link the given modules dynamically. The special keywordnonedisables the build of all modules.
Allow IPv6 sockets to handle IPv4 connections.
This defines the port on whichhttpdwill listen. This port number is used when generating the configuration filehttpd.conf. The default is 80.
Define an alternative executable name. The default is httpd.These options are used to define optional packages.
Generally you can use the following syntax to define an optional package:
Use the package PACKAGE. The default value for ARG is yes.Do not use the package PACKAGE. This is the same as--with-PACKAGE=no. This option is provided byautoconfbut not very useful for the Apache HTTP Server.
TheApache Portable Runtime(APR) is part of the httpd source distribution and will automatically be build together with the HTTP server. If you want to use an already installed APR instead you have to tellconfigurethe path to theapr-configscript. You may set the absolute path and name or the directory to the installed APR.apr-configmust exist within this directory or the subdirectorybin.
The Apache Portable Runtime Utilities (APU) are part of the httpd source distribution and will automatically be build together with the HTTP server. If you want to use an already installed APU instead you have to tellconfigurethe path to theapu-configscript. You may set the absolute path and name or the directory to the installed APU.apu-configmust exist within this directory or the subdirectorybin.
Ifmod_sslhas been enabledconfiguresearches for an installed OpenSSL. You can set the directory path to the SSL/TLS toolkit instead.
configuresearches automatically for an installedzliblibrary if your source configuration requires one (e.g., whenmod_deflateis enabled). You can set the directory path to the compression library instead.
Several features of the Apache HTTP Server, includingmod_authn_dbmandmod_rewrite's DBMRewriteMapuse 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:
If nopathis specified,configurewill search for the include files and libraries of a GNU DBM installation in the usual search paths. An explicitpathwill causeconfigureto look inpath/libandpath/includefor the relevant files. Finally, thepathmay specify specific include and library paths separated by a colon.
Like --with-gdbm, but searches for a New DBM installation.Like --with-gdbm, but searches for a Berkeley DB installation.
Note
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.
ノート
この DBM は APU によって提供されその構成スクリプトに渡されます. それらはすでに --with-apr-util によって定義されたすでにインストール済みの APU を使うときには使えません.
あなたはあなたの HTTP サーバとともにひとつ以上の DBM 実装を使うことができます. 適切な DBM タイプはランタイムの構成で都度構成されます.
Build a statically linked version of the support binaries. This means, a stand-alone executable will be built with all the necessary libraries integrated. Otherwise the support binaries are linked dynamically by default.
Use this option to enablesuexec, 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 configuresuexecare describedbelow.
It is possible to create a statically linked binary of a single support program by using the following options:
Build a statically linked vesion of ab.Build a statically linked version of checkgid.Build a statically linked version of htdbm.Build a statically linked version of htdigest.Build a statically linked version of htpasswd.Build a statically linked version of logresolve.Build a statically linked version of rotatelogs.suexec 構成オプション (configuration options)The following options are used to fine tune the behavior ofsuexec. SeeConfiguring and installing suEXECfor further information.
This defines the path tosuexecbinary. Default is--sbindir(seeFine tuning of installation directories).
This defines the user allowed to callsuexec. It should be the same as the user under whichhttpdnormally runs.
This defines the directory tree under whichsuexecaccess is allowed for executables. Default value is--datadir/htdocs.
Define this as the lowest GID allowed to be a target user for suexec. The default value is 100.This defines the filename of thesuexeclogfile. By default the logfile is namedsuexec_logand located in--logfiledir.
Define the value of the environment variable PATH to be set for processes started bysuexec. Default value is/usr/local/bin:/usr/bin:/bin.
This defines the subdirectory under the user's directory that contains all executables for whichsuexecaccess is allowed. This setting is necessary when you want to usesuexectogether with user-specific directories (as provided bymod_userdir). The default ispublic_html.
Define this as the lowest UID allowed to be a target user for suexec. The default value is 100.Setumaskfor processes started bysuexec. 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.Define the C compiler command to be used for compilation.
Set C compiler flags you want to use for compilation.
Define the C preprocessor command to be used.
Set C/C++ preprocessor flags, e.g.-Iincludedirif you have headers in a nonstandard directoryincludedir.
Set linker flags, e.g.-Llibdirif you have libraries in a nonstandard directorylibdir.
Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to ourmailing lists.
お知らせ
これは Q&A セクションではありません. ここにおかれるコメントはドキュメントやサーバの改善の提案に向けられなければならず, もし無効/オフトピック (# の条件) を満たしたり (# そうであると) 見做された場合は私たちのモデレータによって削除されるかもしれません. Apache HTTP Server をどのように管理するかの質問は私たちの Libera.chat 上の IRC チェンネル, #httpd か私たちのメーリングリストいずれかの方に送られるべきです.