1
Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
4
This file is free documentation; the Free Software Foundation gives
5
unlimited permission to copy, distribute and modify it.
9
The simplest way to compile this package is:
11
1. `cd' to the directory containing the package's source code and type
12
`./configure' to configure the package for your system.
13
2. Type `make' to compile the package.
14
3. Type `make install' to install the programs and any data files and
19
The executable is dynamically linked by default. If you have the necessary
20
static libraries installed, you might want to turn on static linking by typing
22
./configure --enable-static
24
A statically-linked executable takes more disk and memory space; however it
25
runs generally faster and it will work on any similar system independently of
26
the libraries available.
27
By default a single-threaded version of the executable is built, which
28
is fine for machines with a single processor. If the machine the software
29
will run on has multiple processors, you might prefer to take advantage
30
of parallel processing by enabling multi-threading. For this you must run
31
configure with the --enable-threads option:
33
./configure --enable-threads
35
This will allow the program to run with up to 16 simultaneous threads
36
(tasks). If your machine has more than 16 processors, say, 40 (!),
37
you may increase the maximum number of threads allowed by using instead
39
./configure --enable-threads=40
44
Some systems require unusual options for compilation or linking that
45
the `configure' script does not know about. Run `./configure --help'
46
for details on some of the pertinent environment variables.
48
You can give `configure' initial values for variables by setting
49
them in the environment. You can do that on the command line like this:
51
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
57
By default, `make install' will install the package's files in
58
`/usr/local/bin', `/usr/local/man', etc. You can specify an
59
installation prefix other than `/usr/local' by giving `configure' the
60
option `--prefix=PATH'.
62
You can specify separate installation prefixes for
63
architecture-specific files and architecture-independent files. If you
64
give `configure' the option `--exec-prefix=PATH', the package will use
65
PATH as the prefix for installing programs and libraries.
66
Documentation and other data files will still use the regular prefix.
68
In addition, if you use an unusual directory layout you can give
69
options like `--bindir=PATH' to specify different values for particular
70
kinds of files. Run `configure --help' for a list of the directories
71
you can set and what kinds of files go in them.
added
removed
INSTALL
