Debian Codegraph @

INSTALL

raw
1
2 --------------------------------------------------------------
3 Please see README for package specific installation details.
4 --------------------------------------------------------------
5
6 Basic Installation
7 ==================
8
9 These are generic installation instructions.
10
11 The `configure' shell script attempts to guess correct values for
12 various system-dependent variables used during compilation. It uses
13 those values to create a `Makefile' in each directory of the package.
14 It may also create one or more `.h' files containing system-dependent
15 definitions. Finally, it creates a shell script `config.status' that
16 you can run in the future to recreate the current configuration, a file
17 `config.cache' that saves the results of its tests to speed up
18 reconfiguring, and a file `config.log' containing compiler output
19 (useful mainly for debugging `configure').
20
21 If you need to do unusual things to compile the package, please try
22 to figure out how `configure' could check whether to do them, and mail
23 diffs or instructions to the address given in the `README' so they can
24 be considered for the next release. If at some point `config.cache'
25 contains results you don't want to keep, you may remove or edit it.
26
27 The file `configure.in' is used to create `configure' by a program
28 called `autoconf'. You only need `configure.in' if you want to change
29 it or regenerate `configure' using a newer version of `autoconf'.
30
31 The simplest way to compile this package is:
32
33 1. `cd' to the directory containing the package's source code and type
34 `./configure' to configure the package for your system. If you're
35 using `csh' on an old version of System V, you might need to type
36 `sh ./configure' instead to prevent `csh' from trying to execute
37 `configure' itself.
38
39 Running `configure' takes a while. While running, it prints some
40 messages telling which features it is checking for.
41
42 2. Type `make' to compile the package.
43
44 3. Type `make install' to install the programs and any data files and
45 documentation.
46
47 4. You can remove the program binaries and object files from the
48 source code directory by typing `make clean'.
49
50 Compilers and Options
51 =====================
52
53 Some systems require unusual options for compilation or linking that
54 the `configure' script does not know about. You can give `configure'
55 initial values for variables by setting them in the environment. Using
56 a Bourne-compatible shell, you can do that on the command line like
57 this:
58 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
59
60 Or on systems that have the `env' program, you can do it like this:
61 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
62
63 Compiling For Multiple Architectures
64 ====================================
65
66 You can compile the package for more than one kind of computer at the
67 same time, by placing the object files for each architecture in their
68 own directory. To do this, you must use a version of `make' that
69 supports the `VPATH' variable, such as GNU `make'. `cd' to the
70 directory where you want the object files and executables to go and run
71 the `configure' script. `configure' automatically checks for the
72 source code in the directory that `configure' is in and in `..'.
73
74 If you have to use a `make' that does not supports the `VPATH'
75 variable, you have to compile the package for one architecture at a time
76 in the source code directory. After you have installed the package for
77 one architecture, use `make distclean' before reconfiguring for another
78 architecture.
79
80 Installation Names
81 ==================
82
83 By default, `make install' will install the package's files in
84 `/usr/local/bin', `/usr/local/man', etc. You can specify an
85 installation prefix other than `/usr/local' by giving `configure' the
86 option `--prefix=PATH'.
87
88 You can specify separate installation prefixes for
89 architecture-specific files and architecture-independent files. If you
90 give `configure' the option `--exec-prefix=PATH', the package will use
91 PATH as the prefix for installing programs and libraries.
92 Documentation and other data files will still use the regular prefix.
93
94 If the package supports it, you can cause programs to be installed
95 with an extra prefix or suffix on their names by giving `configure' the
96 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
97
98 Optional Features
99 =================
100
101 Some packages pay attention to `--enable-FEATURE' options to
102 `configure', where FEATURE indicates an optional part of the package.
103 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
104 is something like `gnu-as' or `x' (for the X Window System). The
105 `README' should mention any `--enable-' and `--with-' options that the
106 package recognizes.
107
108 For packages that use the X Window System, `configure' can usually
109 find the X include and library files automatically, but if it doesn't,
110 you can use the `configure' options `--x-includes=DIR' and
111 `--x-libraries=DIR' to specify their locations.
112
113 Specifying the System Type
114 ==========================
115
116 There may be some features `configure' can not figure out
117 automatically, but needs to determine by the type of host the package
118 will run on. Usually `configure' can figure that out, but if it prints
119 a message saying it can not guess the host type, give it the
120 `--host=TYPE' option. TYPE can either be a short name for the system
121 type, such as `sun4', or a canonical name with three fields:
122 CPU-COMPANY-SYSTEM
123
124 See the file `config.sub' for the possible values of each field. If
125 `config.sub' isn't included in this package, then this package doesn't
126 need to know the host type.
127
128 If you are building compiler tools for cross-compiling, you can also
129 use the `--target=TYPE' option to select the type of system they will
130 produce code for and the `--build=TYPE' option to select the type of
131 system on which you are compiling the package.
132
133 Sharing Defaults
134 ================
135
136 If you want to set default values for `configure' scripts to share,
137 you can create a site shell script called `config.site' that gives
138 default values for variables like `CC', `cache_file', and `prefix'.
139 `configure' looks for `PREFIX/share/config.site' if it exists, then
140 `PREFIX/etc/config.site' if it exists. Or, you can set the
141 `CONFIG_SITE' environment variable to the location of the site script.
142 A warning: not all `configure' scripts look for a site script.
143
144 Operation Controls
145 ==================
146
147 `configure' recognizes the following options to control how it
148 operates.
149
150 `--cache-file=FILE'
151 Use and save the results of the tests in FILE instead of
152 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
153 debugging `configure'.
154
155 `--help'
156 Print a summary of the options to `configure', and exit.
157
158 `--quiet'
159 `--silent'
160 `-q'
161 Do not print messages saying which checks are being made.
162
163 `--srcdir=DIR'
164 Look for the package's source code in directory DIR. Usually
165 `configure' can determine that directory automatically.
166
167 `--version'
168 Print the version of Autoconf used to generate the `configure'
169 script, and exit.
170
171 `configure' also accepts some other, not widely useful, options.
172