2N/A APACHE INSTALLATION OVERVIEW
2N/A $ ./configure --prefix=PREFIX
2N/A NOTES: * Replace PREFIX with the filesystem path under which
2N/A Apache should be installed. A typical installation
2N/A * Read the section "APR - Unix" below.
2N/A * If you are a developer building Apache directly from
2N/A Subversion, you will need to run ./buildconf before running
2N/A configure. This script bootstraps the build environment and
2N/A requires Python as well as GNU autoconf and libtool. If you
2N/A build Apache from a release tarball, you don't have to run
2N/A * If you want to build a threaded MPM (for instance worker)
2N/A on FreeBSD, be aware that threads do not work well with
2N/A Apache on FreeBSD versions before 5.4-RELEASE. If you wish
2N/A to try a threaded Apache on an earlier version of FreeBSD,
2N/A use the --enable-threads parameter to ./configure in
2N/A addition to the --with-mpm parameter.
2N/A * If you are building directly from Subversion on Mac OS X
2N/A (Darwin), make sure to use GNU Libtool 1.4.2 or newer. All
2N/A recent versions of the developer tools on this platform
2N/A include a sufficiently recent version of GNU Libtool (named
2N/A glibtool, but buildconf knows where to find it).
2N/A For a short impression of what possibilities you have, here is a
2N/A typical example which configures Apache for the installation tree
2N/A additional modules mod_rewrite and mod_speling for later loading
2N/A through the DSO mechanism:
2N/A $ CC="pgcc" CFLAGS="-O2" \
2N/A --enable-rewrite=shared \
2N/A --enable-speling=shared
2N/A The easiest way to find all of the configuration flags for Apache 2.5
2N/A is to run ./configure --help.
2N/A httpd trunk (httpd development version 2.5) can use APR trunk (future
2N/A APR version 2.0) or the combination of the current APR
1.x branch and
2N/A the current APR-util
1.x branch. (APR trunk bundles the features in
2N/A The httpd buildconf step, required when building httpd from Subversion,
2N/A must have access to the APR source. The httpd configure step, always
2N/A required, can configure the APR source in srclib or use a previously-
2N/A APR (and APR-util if using APR
1.x) can be built with httpd from httpd's
2N/A srclib directory or can be built separately, prior to building httpd.
2N/A Building APR with httpd from httpd's srclib directory is required if
2N/A you don't have the compiler which the system APR was built with, and it
2N/A can also be advantageous if you are a developer who will be linking your
2N/A code with httpd or using a debugger to step through server code, as it
2N/A removes the possibility of version or compile-option mismatches with
2N/A APR and APR-util code.
2N/A To use APR trunk in srclib:
2N/A buildconf will find it automaticaly. Use the --with-included-apr
2N/A argument to httpd configure.
2N/A the following commands:
2N/A buildconf will find them automaticaly. Use the --with-included-apr
2N/A argument to httpd configure.
2N/A To use existing checkouts of APR (and APR-util if using APR
1.x):
2N/A httpd buildconf must have access to the source trees. Use these arguments
2N/A --with-apr=[path to apr source] --with-apr-util=[path to apr-util source]
2N/A (Omit --with-apr-util if using APR trunk.)
2N/A httpd configure must have access to a previously build apr. Use these
2N/A arguments to httpd configure:
--with-apr=[path to apr install] --with-apr-util=[path to apr-util install]
(Omit --with-apr-util if using APR trunk.)
The
Apache/Win32 binaries are distributed as Windows Installer packages
mod_ssl plus the openssl library and command line utility. Additional 64 bit
binaries have similarly named -win64-x64 package names. These packages
may be unpacked without "installing" them by using the msiexec /a option.
without any -x86 or -x64 notation) you must compile the package yourself,
see the links mentioned above. Unless you intended to do this, please look
and install that desired .msi package.
The .msi package configures the
httpd.conf file, and installs and starts
the
Apache2.x service for you. It also installs plenty of useful shortcuts
and the taskbar ApacheMonitor. We strongly encourage you to use it.
The Apache HTTP Server group cannot field user's installation questions.
There are many valuable forums to help you get started. Please refer your
questions to the appropriate forum, such as the Users Mailing List at
Thanks for using the Apache HTTP Server, version 2.5.
The Apache Software Foundation