1 Installation Instructions
2 *************************
3
4 Copyright (C) 1994, 1995, 1996, 1999, 2000, 20
5 2006, 2007 Free Software Foundation, Inc.
6
7 This file is free documentation; the Free Soft
8 unlimited permission to copy, distribute and m
9
10 Basic Installation
11 ==================
12
13 Briefly, the shell commands `./configure; make
14 configure, build, and install this package. T
15 more-detailed instructions are generic; see th
16 instructions specific to this package.
17
18 The `configure' shell script attempts to gu
19 various system-dependent variables used during
20 those values to create a `Makefile' in each di
21 It may also create one or more `.h' files cont
22 definitions. Finally, it creates a shell scri
23 you can run in the future to recreate the curr
24 file `config.log' containing compiler output (
25 debugging `configure').
26
27 It can also use an optional file (typically
28 and enabled with `--cache-file=config.cache' o
29 the results of its tests to speed up reconfigu
30 disabled by default to prevent problems with a
31 cache files.
32
33 If you need to do unusual things to compile
34 to figure out how `configure' could check whet
35 diffs or instructions to the address given in
36 be considered for the next release. If you ar
37 some point `config.cache' contains results you
38 may remove or edit it.
39
40 The file `configure.ac' (or `configure.in')
41 `configure' by a program called `autoconf'. Y
42 you want to change it or regenerate `configure
43 of `autoconf'.
44
45 The simplest way to compile this package is:
46
47 1. `cd' to the directory containing the pack
48 `./configure' to configure the package fo
49
50 Running `configure' might take a while.
51 some messages telling which features it i
52
53 2. Type `make' to compile the package.
54
55 3. Optionally, type `make check' to run any
56 the package.
57
58 4. Type `make install' to install the progra
59 documentation.
60
61 5. You can remove the program binaries and o
62 source code directory by typing `make cle
63 files that `configure' created (so you ca
64 a different kind of computer), type `make
65 also a `make maintainer-clean' target, bu
66 for the package's developers. If you use
67 all sorts of other programs in order to r
68 with the distribution.
69
70 6. Often, you can also type `make uninstall'
71 files again.
72
73 Compilers and Options
74 =====================
75
76 Some systems require unusual options for compi
77 `configure' script does not know about. Run `
78 details on some of the pertinent environment v
79
80 You can give `configure' initial values for
81 by setting variables in the command line or in
82 is an example:
83
84 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
85
86 *Note Defining Variables::, for more detail
87
88 Compiling For Multiple Architectures
89 ====================================
90
91 You can compile the package for more than one
92 same time, by placing the object files for eac
93 own directory. To do this, you can use GNU `m
94 directory where you want the object files and
95 the `configure' script. `configure' automatic
96 source code in the directory that `configure'
97
98 With a non-GNU `make', it is safer to compi
99 architecture at a time in the source code dire
100 installed the package for one architecture, us
101 reconfiguring for another architecture.
102
103 Installation Names
104 ==================
105
106 By default, `make install' installs the packag
107 `/usr/local/bin', include files under `/usr/lo
108 can specify an installation prefix other than
109 `configure' the option `--prefix=PREFIX'.
110
111 You can specify separate installation prefi
112 architecture-specific files and architecture-i
113 pass the option `--exec-prefix=PREFIX' to `con
114 PREFIX as the prefix for installing programs a
115 Documentation and other data files still use t
116
117 In addition, if you use an unusual director
118 options like `--bindir=DIR' to specify differe
119 kinds of files. Run `configure --help' for a
120 you can set and what kinds of files go in them
121
122 If the package supports it, you can cause p
123 with an extra prefix or suffix on their names
124 option `--program-prefix=PREFIX' or `--program
125
126 Optional Features
127 =================
128
129 Some packages pay attention to `--enable-FEATU
130 `configure', where FEATURE indicates an option
131 They may also pay attention to `--with-PACKAGE
132 is something like `gnu-as' or `x' (for the X W
133 `README' should mention any `--enable-' and `-
134 package recognizes.
135
136 For packages that use the X Window System,
137 find the X include and library files automatic
138 you can use the `configure' options `--x-inclu
139 `--x-libraries=DIR' to specify their locations
140
141 Specifying the System Type
142 ==========================
143
144 There may be some features `configure' cannot
145 but needs to determine by the type of machine
146 Usually, assuming the package is built to be r
147 architectures, `configure' can figure that out
148 message saying it cannot guess the machine typ
149 `--build=TYPE' option. TYPE can either be a s
150 type, such as `sun4', or a canonical name whic
151
152 CPU-COMPANY-SYSTEM
153
154 where SYSTEM can have one of these forms:
155
156 OS KERNEL-OS
157
158 See the file `config.sub' for the possible
159 `config.sub' isn't included in this package, t
160 need to know the machine type.
161
162 If you are _building_ compiler tools for cr
163 use the option `--target=TYPE' to select the t
164 produce code for.
165
166 If you want to _use_ a cross compiler, that
167 platform different from the build platform, yo
168 "host" platform (i.e., that on which the gener
169 eventually be run) with `--host=TYPE'.
170
171 Sharing Defaults
172 ================
173
174 If you want to set default values for `configu
175 can create a site shell script called `config.
176 values for variables like `CC', `cache_file',
177 `configure' looks for `PREFIX/share/config.sit
178 `PREFIX/etc/config.site' if it exists. Or, yo
179 `CONFIG_SITE' environment variable to the loca
180 A warning: not all `configure' scripts look fo
181
182 Defining Variables
183 ==================
184
185 Variables not defined in a site shell script c
186 environment passed to `configure'. However, s
187 configure again during the build, and the cust
188 variables may be lost. In order to avoid this
189 them in the `configure' command line, using `V
190
191 ./configure CC=/usr/local2/bin/gcc
192
193 causes the specified `gcc' to be used as the C
194 overridden in the site shell script).
195
196 Unfortunately, this technique does not work fo
197 an Autoconf bug. Until the bug is fixed you c
198
199 CONFIG_SHELL=/bin/bash /bin/bash ./config
200
201 `configure' Invocation
202 ======================
203
204 `configure' recognizes the following options t
205
206 `--help'
207 `-h'
208 Print a summary of the options to `config
209
210 `--version'
211 `-V'
212 Print the version of Autoconf used to gen
213 script, and exit.
214
215 `--cache-file=FILE'
216 Enable the cache: use and save the result
217 traditionally `config.cache'. FILE defau
218 disable caching.
219
220 `--config-cache'
221 `-C'
222 Alias for `--cache-file=config.cache'.
223
224 `--quiet'
225 `--silent'
226 `-q'
227 Do not print messages saying which checks
228 suppress all normal output, redirect it t
229 messages will still be shown).
230
231 `--srcdir=DIR'
232 Look for the package's source code in dir
233 `configure' can determine that directory
234
235 `configure' also accepts some other, not widel
236 `configure --help' for more details.
237
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.