Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
100644 180 lines (140 sloc) 7.627 kb
38766791 »
2006-09-11 move
1 Basic Installation
2 ==================
0b325987 »
2007-11-01 * docs autogen INSTALL UPGRADING
4 These are generic installation instructions, and describe in
5 general how to use ./configure. For Amanda-specific installation
6 instructions, including system-specific notes, please see
38766791 »
2006-09-11 move
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 `' is used to create `configure' by a program
26 called `autoconf'. You only need `' 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
35 `configure' itself.
37 Running `configure' takes a while. 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
43 the package.
45 4. Type `make install' to install the programs and any data files and
46 documentation.
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.
57 Compilers and Options
58 =====================
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
64 this:
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
85 architecture.
87 Installation Names
88 ==================
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 If the package supports it, you can cause programs to be installed
102 with an extra prefix or suffix on their names by giving `configure' the
103 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
105 Optional Features
106 =================
108 Some packages pay attention to `--enable-FEATURE' options to
109 `configure', where FEATURE indicates an optional part of the package.
110 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
111 is something like `gnu-as' or `x' (for the X Window System). The
112 `README' should mention any `--enable-' and `--with-' options that the
113 package recognizes.
115 For packages that use the X Window System, `configure' can usually
116 find the X include and library files automatically, but if it doesn't,
117 you can use the `configure' options `--x-includes=DIR' and
118 `--x-libraries=DIR' to specify their locations.
120 Specifying the System Type
121 ==========================
123 There may be some features `configure' can not figure out
124 automatically, but needs to determine by the type of host the package
125 will run on. Usually `configure' can figure that out, but if it prints
126 a message saying it can not guess the host type, give it the
127 `--host=TYPE' option. TYPE can either be a short name for the system
128 type, such as `sun4', or a canonical name with three fields:
131 See the file `config.sub' for the possible values of each field. If
132 `config.sub' isn't included in this package, then this package doesn't
133 need to know the host type.
135 If you are building compiler tools for cross-compiling, you can also
136 use the `--target=TYPE' option to select the type of system they will
137 produce code for and the `--build=TYPE' option to select the type of
138 system on which you are compiling the package.
140 Sharing Defaults
141 ================
143 If you want to set default values for `configure' scripts to share,
144 you can create a site shell script called `' that gives
145 default values for variables like `CC', `cache_file', and `prefix'.
146 `configure' looks for `PREFIX/share/' if it exists, then
147 `PREFIX/etc/' if it exists. Or, you can set the
148 `CONFIG_SITE' environment variable to the location of the site script.
149 A warning: not all `configure' scripts look for a site script.
151 Operation Controls
152 ==================
154 `configure' recognizes the following options to control how it
155 operates.
157 `--cache-file=FILE'
158 Use and save the results of the tests in FILE instead of
159 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
160 debugging `configure'.
162 `--help'
163 Print a summary of the options to `configure', and exit.
165 `--quiet'
166 `--silent'
167 `-q'
168 Do not print messages saying which checks are being made.
170 `--srcdir=DIR'
171 Look for the package's source code in directory DIR. Usually
172 `configure' can determine that directory automatically.
174 `--version'
175 Print the version of Autoconf used to generate the `configure'
176 script, and exit.
178 `configure' also accepts some other, not widely useful, options.
Something went wrong with that request. Please try again.