/[public]/psiconv/trunk/INSTALL
ViewVC logotype

Diff of /psiconv/trunk/INSTALL

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 137 Revision 254
1Installation Instructions
2*************************
3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
5Software Foundation, Inc.
6
7This file is free documentation; the Free Software Foundation gives
8unlimited permission to copy, distribute and modify it.
9
1Basic Installation 10Basic Installation
2================== 11==================
3 12
4 These are generic installation instructions. 13These are generic installation instructions.
5 14
6 The `configure' shell script attempts to guess correct values for 15 The `configure' shell script attempts to guess correct values for
7various system-dependent variables used during compilation. It uses 16various system-dependent variables used during compilation. It uses
8those values to create a `Makefile' in each directory of the package. 17those values to create a `Makefile' in each directory of the package.
9It may also create one or more `.h' files containing system-dependent 18It may also create one or more `.h' files containing system-dependent
10definitions. Finally, it creates a shell script `config.status' that 19definitions. Finally, it creates a shell script `config.status' that
11you can run in the future to recreate the current configuration, a file 20you can run in the future to recreate the current configuration, and a
12`config.cache' that saves the results of its tests to speed up 21file `config.log' containing compiler output (useful mainly for
13reconfiguring, and a file `config.log' containing compiler output 22debugging `configure').
14(useful mainly for debugging `configure'). 23
24 It can also use an optional file (typically called `config.cache'
25and enabled with `--cache-file=config.cache' or simply `-C') that saves
26the results of its tests to speed up reconfiguring. (Caching is
27disabled by default to prevent problems with accidental use of stale
28cache files.)
15 29
16 If you need to do unusual things to compile the package, please try 30 If you need to do unusual things to compile the package, please try
17to figure out how `configure' could check whether to do them, and mail 31to figure out how `configure' could check whether to do them, and mail
18diffs or instructions to the address given in the `README' so they can 32diffs or instructions to the address given in the `README' so they can
19be considered for the next release. If at some point `config.cache' 33be considered for the next release. If you are using the cache, and at
20contains results you don't want to keep, you may remove or edit it. 34some point `config.cache' contains results you don't want to keep, you
35may remove or edit it.
21 36
22 The file `configure.in' is used to create `configure' by a program 37 The file `configure.ac' (or `configure.in') is used to create
23called `autoconf'. You only need `configure.in' if you want to change 38`configure' by a program called `autoconf'. You only need
24it or regenerate `configure' using a newer version of `autoconf'. 39`configure.ac' if you want to change it or regenerate `configure' using
40a newer version of `autoconf'.
25 41
26The simplest way to compile this package is: 42The simplest way to compile this package is:
27 43
28 1. `cd' to the directory containing the package's source code and type 44 1. `cd' to the directory containing the package's source code and type
29 `./configure' to configure the package for your system. If you're 45 `./configure' to configure the package for your system. If you're
52 with the distribution. 68 with the distribution.
53 69
54Compilers and Options 70Compilers and Options
55===================== 71=====================
56 72
57 Some systems require unusual options for compilation or linking that 73Some systems require unusual options for compilation or linking that the
58the `configure' script does not know about. You can give `configure' 74`configure' script does not know about. Run `./configure --help' for
59initial values for variables by setting them in the environment. Using 75details on some of the pertinent environment variables.
60a Bourne-compatible shell, you can do that on the command line like
61this:
62 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
63 76
64Or on systems that have the `env' program, you can do it like this: 77 You can give `configure' initial values for configuration parameters
65 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure 78by setting variables in the command line or in the environment. Here
79is an example:
80
81 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
82
83 *Note Defining Variables::, for more details.
66 84
67Compiling For Multiple Architectures 85Compiling For Multiple Architectures
68==================================== 86====================================
69 87
70 You can compile the package for more than one kind of computer at the 88You can compile the package for more than one kind of computer at the
71same time, by placing the object files for each architecture in their 89same time, by placing the object files for each architecture in their
72own directory. To do this, you must use a version of `make' that 90own directory. To do this, you must use a version of `make' that
73supports the `VPATH' variable, such as GNU `make'. `cd' to the 91supports the `VPATH' variable, such as GNU `make'. `cd' to the
74directory where you want the object files and executables to go and run 92directory where you want the object files and executables to go and run
75the `configure' script. `configure' automatically checks for the 93the `configure' script. `configure' automatically checks for the
76source code in the directory that `configure' is in and in `..'. 94source code in the directory that `configure' is in and in `..'.
77 95
78 If you have to use a `make' that does not supports the `VPATH' 96 If you have to use a `make' that does not support the `VPATH'
79variable, you have to compile the package for one architecture at a time 97variable, you have to compile the package for one architecture at a
80in the source code directory. After you have installed the package for 98time in the source code directory. After you have installed the
81one architecture, use `make distclean' before reconfiguring for another 99package for one architecture, use `make distclean' before reconfiguring
82architecture. 100for another architecture.
83 101
84Installation Names 102Installation Names
85================== 103==================
86 104
87 By default, `make install' will install the package's files in 105By default, `make install' will install the package's files in
88`/usr/local/bin', `/usr/local/man', etc. You can specify an 106`/usr/local/bin', `/usr/local/man', etc. You can specify an
89installation prefix other than `/usr/local' by giving `configure' the 107installation prefix other than `/usr/local' by giving `configure' the
90option `--prefix=PATH'. 108option `--prefix=PREFIX'.
91 109
92 You can specify separate installation prefixes for 110 You can specify separate installation prefixes for
93architecture-specific files and architecture-independent files. If you 111architecture-specific files and architecture-independent files. If you
94give `configure' the option `--exec-prefix=PATH', the package will use 112give `configure' the option `--exec-prefix=PREFIX', the package will
95PATH as the prefix for installing programs and libraries. 113use PREFIX as the prefix for installing programs and libraries.
96Documentation and other data files will still use the regular prefix. 114Documentation and other data files will still use the regular prefix.
97 115
98 In addition, if you use an unusual directory layout you can give 116 In addition, if you use an unusual directory layout you can give
99options like `--bindir=PATH' to specify different values for particular 117options like `--bindir=DIR' to specify different values for particular
100kinds of files. Run `configure --help' for a list of the directories 118kinds of files. Run `configure --help' for a list of the directories
101you can set and what kinds of files go in them. 119you can set and what kinds of files go in them.
102 120
103 If the package supports it, you can cause programs to be installed 121 If the package supports it, you can cause programs to be installed
104with an extra prefix or suffix on their names by giving `configure' the 122with an extra prefix or suffix on their names by giving `configure' the
105option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 123option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
106 124
107Optional Features 125Optional Features
108================= 126=================
109 127
110 Some packages pay attention to `--enable-FEATURE' options to 128Some packages pay attention to `--enable-FEATURE' options to
111`configure', where FEATURE indicates an optional part of the package. 129`configure', where FEATURE indicates an optional part of the package.
112They may also pay attention to `--with-PACKAGE' options, where PACKAGE 130They may also pay attention to `--with-PACKAGE' options, where PACKAGE
113is something like `gnu-as' or `x' (for the X Window System). The 131is something like `gnu-as' or `x' (for the X Window System). The
114`README' should mention any `--enable-' and `--with-' options that the 132`README' should mention any `--enable-' and `--with-' options that the
115package recognizes. 133package recognizes.
120`--x-libraries=DIR' to specify their locations. 138`--x-libraries=DIR' to specify their locations.
121 139
122Specifying the System Type 140Specifying the System Type
123========================== 141==========================
124 142
125 There may be some features `configure' can not figure out 143There may be some features `configure' cannot figure out automatically,
126automatically, but needs to determine by the type of host the package 144but needs to determine by the type of machine the package will run on.
145Usually, assuming the package is built to be run on the _same_
127will run on. Usually `configure' can figure that out, but if it prints 146architectures, `configure' can figure that out, but if it prints a
128a message saying it can not guess the host type, give it the 147message saying it cannot guess the machine type, give it the
129`--host=TYPE' option. TYPE can either be a short name for the system 148`--build=TYPE' option. TYPE can either be a short name for the system
130type, such as `sun4', or a canonical name with three fields: 149type, such as `sun4', or a canonical name which has the form:
150
131 CPU-COMPANY-SYSTEM 151 CPU-COMPANY-SYSTEM
132 152
153where SYSTEM can have one of these forms:
154
155 OS KERNEL-OS
156
133See the file `config.sub' for the possible values of each field. If 157 See the file `config.sub' for the possible values of each field. If
134`config.sub' isn't included in this package, then this package doesn't 158`config.sub' isn't included in this package, then this package doesn't
135need to know the host type. 159need to know the machine type.
136 160
137 If you are building compiler tools for cross-compiling, you can also 161 If you are _building_ compiler tools for cross-compiling, you should
138use the `--target=TYPE' option to select the type of system they will 162use the `--target=TYPE' option to select the type of system they will
139produce code for and the `--build=TYPE' option to select the type of 163produce code for.
140system on which you are compiling the package. 164
165 If you want to _use_ a cross compiler, that generates code for a
166platform different from the build platform, you should specify the
167"host" platform (i.e., that on which the generated programs will
168eventually be run) with `--host=TYPE'.
141 169
142Sharing Defaults 170Sharing Defaults
143================ 171================
144 172
145 If you want to set default values for `configure' scripts to share, 173If you want to set default values for `configure' scripts to share, you
146you can create a site shell script called `config.site' that gives 174can create a site shell script called `config.site' that gives default
147default values for variables like `CC', `cache_file', and `prefix'. 175values for variables like `CC', `cache_file', and `prefix'.
148`configure' looks for `PREFIX/share/config.site' if it exists, then 176`configure' looks for `PREFIX/share/config.site' if it exists, then
149`PREFIX/etc/config.site' if it exists. Or, you can set the 177`PREFIX/etc/config.site' if it exists. Or, you can set the
150`CONFIG_SITE' environment variable to the location of the site script. 178`CONFIG_SITE' environment variable to the location of the site script.
151A warning: not all `configure' scripts look for a site script. 179A warning: not all `configure' scripts look for a site script.
152 180
153Operation Controls 181Defining Variables
154================== 182==================
155 183
184Variables not defined in a site shell script can be set in the
185environment passed to `configure'. However, some packages may run
186configure again during the build, and the customized values of these
187variables may be lost. In order to avoid this problem, you should set
188them in the `configure' command line, using `VAR=value'. For example:
189
190 ./configure CC=/usr/local2/bin/gcc
191
192will cause the specified gcc to be used as the C compiler (unless it is
193overridden in the site shell script).
194
195`configure' Invocation
196======================
197
156 `configure' recognizes the following options to control how it 198`configure' recognizes the following options to control how it operates.
157operates. 199
200`--help'
201`-h'
202 Print a summary of the options to `configure', and exit.
203
204`--version'
205`-V'
206 Print the version of Autoconf used to generate the `configure'
207 script, and exit.
158 208
159`--cache-file=FILE' 209`--cache-file=FILE'
160 Use and save the results of the tests in FILE instead of 210 Enable the cache: use and save the results of the tests in FILE,
161 `./config.cache'. Set FILE to `/dev/null' to disable caching, for 211 traditionally `config.cache'. FILE defaults to `/dev/null' to
162 debugging `configure'. 212 disable caching.
163 213
164`--help' 214`--config-cache'
165 Print a summary of the options to `configure', and exit. 215`-C'
216 Alias for `--cache-file=config.cache'.
166 217
167`--quiet' 218`--quiet'
168`--silent' 219`--silent'
169`-q' 220`-q'
170 Do not print messages saying which checks are being made. To 221 Do not print messages saying which checks are being made. To
173 224
174`--srcdir=DIR' 225`--srcdir=DIR'
175 Look for the package's source code in directory DIR. Usually 226 Look for the package's source code in directory DIR. Usually
176 `configure' can determine that directory automatically. 227 `configure' can determine that directory automatically.
177 228
178`--version'
179 Print the version of Autoconf used to generate the `configure'
180 script, and exit.
181
182`configure' also accepts some other, not widely useful, options. 229`configure' also accepts some other, not widely useful, options. Run
230`configure --help' for more details.
231

Legend:
Removed from v.137  
changed lines
  Added in v.254

frodo@frodo.looijaard.name
ViewVC Help
Powered by ViewVC 1.1.26