1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
APACHE INSTALLATION OVERVIEW
Quick Start - Unix
------------------
For complete installation documentation, see [ht]docs/manual/install.html or
http://httpd.apache.org/docs/trunk/install.html
$ ./configure --prefix=PREFIX
$ make
$ make install
$ PREFIX/bin/apachectl start
NOTES: * Replace PREFIX with the filesystem path under which
Apache should be installed. A typical installation
might use "/usr/local/apache2" for PREFIX (without the
quotes).
* Read the section "APR - Unix" below.
* If you are a developer building Apache directly from
Subversion, you will need to run ./buildconf before running
configure. This script bootstraps the build environment and
requires Python as well as GNU autoconf and libtool. If you
build Apache from a release tarball, you don't have to run
buildconf.
* If you want to build a threaded MPM (for instance worker)
on FreeBSD, be aware that threads do not work well with
Apache on FreeBSD versions before 5.4-RELEASE. If you wish
to try a threaded Apache on an earlier version of FreeBSD,
use the --enable-threads parameter to ./configure in
addition to the --with-mpm parameter.
* If you are building directly from Subversion on Mac OS X
(Darwin), make sure to use GNU Libtool 1.4.2 or newer. All
recent versions of the developer tools on this platform
include a sufficiently recent version of GNU Libtool (named
glibtool, but buildconf knows where to find it).
For a short impression of what possibilities you have, here is a
typical example which configures Apache for the installation tree
/sw/pkg/apache with a particular compiler and flags plus the two
additional modules mod_rewrite and mod_speling for later loading
through the DSO mechanism:
$ CC="pgcc" CFLAGS="-O2" \
./configure --prefix=/sw/pkg/apache \
--enable-rewrite=shared \
--enable-speling=shared
The easiest way to find all of the configuration flags for Apache 2.5
is to run ./configure --help.
APR - Unix
----------
httpd trunk (httpd development version 2.5) can use APR trunk (future
APR version 2.0) or the combination of the current APR 1.x branch and
the current APR-util 1.x branch. (APR trunk bundles the features in
APR-util 1.x.)
The httpd buildconf step, required when building httpd from Subversion,
must have access to the APR source. The httpd configure step, always
required, can configure the APR source in srclib or use a previously-
built APR.
APR (and APR-util if using APR 1.x) can be built with httpd from httpd's
srclib directory or can be built separately, prior to building httpd.
Building APR with httpd from httpd's srclib directory is required if
you don't have the compiler which the system APR was built with, and it
can also be advantageous if you are a developer who will be linking your
code with httpd or using a debugger to step through server code, as it
removes the possibility of version or compile-option mismatches with
APR and APR-util code.
To use APR trunk in srclib:
Check out APR trunk in srclib/apr with the following command:
svn co http://svn.apache.org/repos/asf/apr/apr/trunk srclib/apr
buildconf will find it automatically. Use the --with-included-apr
argument to httpd configure.
To use APR 1.x and APR-util 1.x in srclib:
Check out the current branches as srclib/apr and srclib/apr-util with
the following commands:
svn co http://svn.apache.org/repos/asf/apr/apr/branches/1.5.x srclib/apr
svn co http://svn.apache.org/repos/asf/apr/apr-util/branches/1.5.x srclib/apr-util
buildconf will find them automatically. Use the --with-included-apr
argument to httpd configure.
To use existing checkouts of APR (and APR-util if using APR 1.x):
httpd buildconf must have access to the source trees. Use these arguments
to httpd buildconf:
--with-apr=[path to apr source] --with-apr-util=[path to apr-util source]
(Omit --with-apr-util if using APR trunk.)
httpd configure must have access to a previously build apr. Use these
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.)
Quick Start - Windows
---------------------
For complete documentation, see manual/platform/windows.html.en or
http://httpd.apache.org/docs/trunk/platform/windows.html.
The Apache/Win32 binaries are distributed as Windows Installer packages
(.msi) named httpd-2.5.xx-win32-x86-no_ssl.msi for a version without mod_ssl
and httpd-2.5.xx-win32-x86-openssl-1.0.1x.msi for a version including the
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.
If you have unpacked a source distribution (named httpd-2.5.x-win32-src.zip,
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
again for an .msi package in http://www.apache.org/dist/httpd/binaries/win32/
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.
Postscript
----------
To obtain help with installation problems, please see the resources at
<http://httpd.apache.org/support.html>
Thanks for using the Apache HTTP Server, version 2.5.
The Apache Software Foundation
http://www.apache.org/
|
