4
These are generic installation instructions that apply to systems that
5
can run the `configure' shell script - Unix systems and any that imitate
6
it. They are not specific to PCRE. There are PCRE-specific instructions
7
for non-Unix systems in the file NON-UNIX-USE.
9
The `configure' shell script attempts to guess correct values for
10
various system-dependent variables used during compilation. It uses
11
those values to create a `Makefile' in each directory of the package.
12
It may also create one or more `.h' files containing system-dependent
13
definitions. Finally, it creates a shell script `config.status' that
14
you can run in the future to recreate the current configuration, a file
15
`config.cache' that saves the results of its tests to speed up
16
reconfiguring, and a file `config.log' containing compiler output
17
(useful mainly for debugging `configure').
19
If you need to do unusual things to compile the package, please try
20
to figure out how `configure' could check whether to do them, and mail
21
diffs or instructions to the address given in the `README' so they can
22
be considered for the next release. If at some point `config.cache'
23
contains results you don't want to keep, you may remove or edit it.
25
The file `configure.in' is used to create `configure' by a program
26
called `autoconf'. You only need `configure.in' if you want to change
27
it or regenerate `configure' using a newer version of `autoconf'.
29
The simplest way to compile this package is:
31
1. `cd' to the directory containing the package's source code and type
32
`./configure' to configure the package for your system. If you're
33
using `csh' on an old version of System V, you might need to type
34
`sh ./configure' instead to prevent `csh' from trying to execute
37
Running `configure' takes awhile. While running, it prints some
38
messages telling which features it is checking for.
40
2. Type `make' to compile the package.
42
3. Optionally, type `make check' to run any self-tests that come with
45
4. Type `make install' to install the programs and any data files and
48
5. You can remove the program binaries and object files from the
49
source code directory by typing `make clean'. To also remove the
50
files that `configure' created (so you can compile the package for
51
a different kind of computer), type `make distclean'. There is
52
also a `make maintainer-clean' target, but that is intended mainly
53
for the package's developers. If you use it, you may have to get
54
all sorts of other programs in order to regenerate files that came
55
with the distribution.
60
Some systems require unusual options for compilation or linking that
61
the `configure' script does not know about. You can give `configure'
62
initial values for variables by setting them in the environment. Using
63
a Bourne-compatible shell, you can do that on the command line like
65
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
67
Or on systems that have the `env' program, you can do it like this:
68
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
70
Compiling For Multiple Architectures
71
====================================
73
You can compile the package for more than one kind of computer at the
74
same time, by placing the object files for each architecture in their
75
own directory. To do this, you must use a version of `make' that
76
supports the `VPATH' variable, such as GNU `make'. `cd' to the
77
directory where you want the object files and executables to go and run
78
the `configure' script. `configure' automatically checks for the
79
source code in the directory that `configure' is in and in `..'.
81
If you have to use a `make' that does not supports the `VPATH'
82
variable, you have to compile the package for one architecture at a time
83
in the source code directory. After you have installed the package for
84
one architecture, use `make distclean' before reconfiguring for another
90
By default, `make install' will install the package's files in
91
`/usr/local/bin', `/usr/local/man', etc. You can specify an
92
installation prefix other than `/usr/local' by giving `configure' the
93
option `--prefix=PATH'.
95
You can specify separate installation prefixes for
96
architecture-specific files and architecture-independent files. If you
97
give `configure' the option `--exec-prefix=PATH', the package will use
98
PATH as the prefix for installing programs and libraries.
99
Documentation and other data files will still use the regular prefix.
101
In addition, if you use an unusual directory layout you can give
102
options like `--bindir=PATH' to specify different values for particular
103
kinds of files. Run `configure --help' for a list of the directories
104
you can set and what kinds of files go in them.
106
If the package supports it, you can cause programs to be installed
107
with an extra prefix or suffix on their names by giving `configure' the
108
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
113
Some packages pay attention to `--enable-FEATURE' options to
114
`configure', where FEATURE indicates an optional part of the package.
115
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
116
is something like `gnu-as' or `x' (for the X Window System). The
117
`README' should mention any `--enable-' and `--with-' options that the
120
For packages that use the X Window System, `configure' can usually
121
find the X include and library files automatically, but if it doesn't,
122
you can use the `configure' options `--x-includes=DIR' and
123
`--x-libraries=DIR' to specify their locations.
125
Specifying the System Type
126
==========================
128
There may be some features `configure' can not figure out
129
automatically, but needs to determine by the type of host the package
130
will run on. Usually `configure' can figure that out, but if it prints
131
a message saying it can not guess the host type, give it the
132
`--host=TYPE' option. TYPE can either be a short name for the system
133
type, such as `sun4', or a canonical name with three fields:
136
See the file `config.sub' for the possible values of each field. If
137
`config.sub' isn't included in this package, then this package doesn't
138
need to know the host type.
140
If you are building compiler tools for cross-compiling, you can also
141
use the `--target=TYPE' option to select the type of system they will
142
produce code for and the `--build=TYPE' option to select the type of
143
system on which you are compiling the package.
148
If you want to set default values for `configure' scripts to share,
149
you can create a site shell script called `config.site' that gives
150
default values for variables like `CC', `cache_file', and `prefix'.
151
`configure' looks for `PREFIX/share/config.site' if it exists, then
152
`PREFIX/etc/config.site' if it exists. Or, you can set the
153
`CONFIG_SITE' environment variable to the location of the site script.
154
A warning: not all `configure' scripts look for a site script.
159
`configure' recognizes the following options to control how it
163
Use and save the results of the tests in FILE instead of
164
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
165
debugging `configure'.
168
Print a summary of the options to `configure', and exit.
173
Do not print messages saying which checks are being made. To
174
suppress all normal output, redirect it to `/dev/null' (any error
175
messages will still be shown).
178
Look for the package's source code in directory DIR. Usually
179
`configure' can determine that directory automatically.
182
Print the version of Autoconf used to generate the `configure'
185
`configure' also accepts some other, not widely useful, options.