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

Diff of /psiconv/trunk/INSTALL

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

Revision 147 Revision 346
1Installation Instructions
2*************************
3
1Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, 4Copyright (C) 1994-1996, 1999-2002, 2004-2011 Free Software Foundation,
2Inc. 5Inc.
3 6
4 This file is free documentation; the Free Software Foundation gives 7 Copying and distribution of this file, with or without modification,
5unlimited permission to copy, distribute and modify it. 8are permitted in any medium without royalty provided the copyright
9notice and this notice are preserved. This file is offered as-is,
10without warranty of any kind.
6 11
7Basic Installation 12Basic Installation
8================== 13==================
9 14
10 These are generic installation instructions. 15 Briefly, the shell commands `./configure; make; make install' should
16configure, build, and install this package. The following
17more-detailed instructions are generic; see the `README' file for
18instructions specific to this package. Some packages provide this
19`INSTALL' file but do not implement all of the features documented
20below. The lack of an optional feature in a given package is not
21necessarily a bug. More recommendations for GNU packages can be found
22in *note Makefile Conventions: (standards)Makefile Conventions.
11 23
12 The `configure' shell script attempts to guess correct values for 24 The `configure' shell script attempts to guess correct values for
13various system-dependent variables used during compilation. It uses 25various system-dependent variables used during compilation. It uses
14those values to create a `Makefile' in each directory of the package. 26those values to create a `Makefile' in each directory of the package.
15It may also create one or more `.h' files containing system-dependent 27It may also create one or more `.h' files containing system-dependent
18file `config.log' containing compiler output (useful mainly for 30file `config.log' containing compiler output (useful mainly for
19debugging `configure'). 31debugging `configure').
20 32
21 It can also use an optional file (typically called `config.cache' 33 It can also use an optional file (typically called `config.cache'
22and enabled with `--cache-file=config.cache' or simply `-C') that saves 34and enabled with `--cache-file=config.cache' or simply `-C') that saves
23the results of its tests to speed up reconfiguring. (Caching is 35the results of its tests to speed up reconfiguring. Caching is
24disabled by default to prevent problems with accidental use of stale 36disabled by default to prevent problems with accidental use of stale
25cache files.) 37cache files.
26 38
27 If you need to do unusual things to compile the package, please try 39 If you need to do unusual things to compile the package, please try
28to figure out how `configure' could check whether to do them, and mail 40to figure out how `configure' could check whether to do them, and mail
29diffs or instructions to the address given in the `README' so they can 41diffs or instructions to the address given in the `README' so they can
30be considered for the next release. If you are using the cache, and at 42be considered for the next release. If you are using the cache, and at
31some point `config.cache' contains results you don't want to keep, you 43some point `config.cache' contains results you don't want to keep, you
32may remove or edit it. 44may remove or edit it.
33 45
34 The file `configure.ac' (or `configure.in') is used to create 46 The file `configure.ac' (or `configure.in') is used to create
35`configure' by a program called `autoconf'. You only need 47`configure' by a program called `autoconf'. You need `configure.ac' if
36`configure.ac' if you want to change it or regenerate `configure' using 48you want to change it or regenerate `configure' using a newer version
37a newer version of `autoconf'. 49of `autoconf'.
38 50
39The simplest way to compile this package is: 51 The simplest way to compile this package is:
40 52
41 1. `cd' to the directory containing the package's source code and type 53 1. `cd' to the directory containing the package's source code and type
42 `./configure' to configure the package for your system. If you're 54 `./configure' to configure the package for your system.
43 using `csh' on an old version of System V, you might need to type
44 `sh ./configure' instead to prevent `csh' from trying to execute
45 `configure' itself.
46 55
47 Running `configure' takes awhile. While running, it prints some 56 Running `configure' might take a while. While running, it prints
48 messages telling which features it is checking for. 57 some messages telling which features it is checking for.
49 58
50 2. Type `make' to compile the package. 59 2. Type `make' to compile the package.
51 60
52 3. Optionally, type `make check' to run any self-tests that come with 61 3. Optionally, type `make check' to run any self-tests that come with
53 the package. 62 the package, generally using the just-built uninstalled binaries.
54 63
55 4. Type `make install' to install the programs and any data files and 64 4. Type `make install' to install the programs and any data files and
56 documentation. 65 documentation. When installing into a prefix owned by root, it is
66 recommended that the package be configured and built as a regular
67 user, and only the `make install' phase executed with root
68 privileges.
57 69
70 5. Optionally, type `make installcheck' to repeat any self-tests, but
71 this time using the binaries in their final installed location.
72 This target does not install anything. Running this target as a
73 regular user, particularly if the prior `make install' required
74 root privileges, verifies that the installation completed
75 correctly.
76
58 5. You can remove the program binaries and object files from the 77 6. You can remove the program binaries and object files from the
59 source code directory by typing `make clean'. To also remove the 78 source code directory by typing `make clean'. To also remove the
60 files that `configure' created (so you can compile the package for 79 files that `configure' created (so you can compile the package for
61 a different kind of computer), type `make distclean'. There is 80 a different kind of computer), type `make distclean'. There is
62 also a `make maintainer-clean' target, but that is intended mainly 81 also a `make maintainer-clean' target, but that is intended mainly
63 for the package's developers. If you use it, you may have to get 82 for the package's developers. If you use it, you may have to get
64 all sorts of other programs in order to regenerate files that came 83 all sorts of other programs in order to regenerate files that came
65 with the distribution. 84 with the distribution.
66 85
86 7. Often, you can also type `make uninstall' to remove the installed
87 files again. In practice, not all packages have tested that
88 uninstallation works correctly, even though it is required by the
89 GNU Coding Standards.
90
91 8. Some packages, particularly those that use Automake, provide `make
92 distcheck', which can by used by developers to test that all other
93 targets like `make install' and `make uninstall' work correctly.
94 This target is generally not run by end users.
95
67Compilers and Options 96Compilers and Options
68===================== 97=====================
69 98
70 Some systems require unusual options for compilation or linking that 99 Some systems require unusual options for compilation or linking that
71the `configure' script does not know about. Run `./configure --help' 100the `configure' script does not know about. Run `./configure --help'
72for details on some of the pertinent environment variables. 101for details on some of the pertinent environment variables.
73 102
74 You can give `configure' initial values for variables by setting 103 You can give `configure' initial values for configuration parameters
75them in the environment. You can do that on the command line like this: 104by setting variables in the command line or in the environment. Here
105is an example:
76 106
77 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix 107 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
78 108
79 *Note Defining Variables::, for more details. 109 *Note Defining Variables::, for more details.
80 110
81Compiling For Multiple Architectures 111Compiling For Multiple Architectures
82==================================== 112====================================
83 113
84 You can compile the package for more than one kind of computer at the 114 You can compile the package for more than one kind of computer at the
85same time, by placing the object files for each architecture in their 115same time, by placing the object files for each architecture in their
86own directory. To do this, you must use a version of `make' that 116own directory. To do this, you can use GNU `make'. `cd' to the
87supports the `VPATH' variable, such as GNU `make'. `cd' to the
88directory where you want the object files and executables to go and run 117directory where you want the object files and executables to go and run
89the `configure' script. `configure' automatically checks for the 118the `configure' script. `configure' automatically checks for the
90source code in the directory that `configure' is in and in `..'. 119source code in the directory that `configure' is in and in `..'. This
120is known as a "VPATH" build.
91 121
92 If you have to use a `make' that does not support the `VPATH' 122 With a non-GNU `make', it is safer to compile the package for one
93variable, you have to compile the package for one architecture at a
94time in the source code directory. After you have installed the 123architecture at a time in the source code directory. After you have
95package for one architecture, use `make distclean' before reconfiguring 124installed the package for one architecture, use `make distclean' before
96for another architecture. 125reconfiguring for another architecture.
126
127 On MacOS X 10.5 and later systems, you can create libraries and
128executables that work on multiple system types--known as "fat" or
129"universal" binaries--by specifying multiple `-arch' options to the
130compiler but only a single `-arch' option to the preprocessor. Like
131this:
132
133 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
134 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
135 CPP="gcc -E" CXXCPP="g++ -E"
136
137 This is not guaranteed to produce working output in all cases, you
138may have to build one architecture at a time and combine the results
139using the `lipo' tool if you have problems.
97 140
98Installation Names 141Installation Names
99================== 142==================
100 143
101 By default, `make install' will install the package's files in 144 By default, `make install' installs the package's commands under
102`/usr/local/bin', `/usr/local/man', etc. You can specify an 145`/usr/local/bin', include files under `/usr/local/include', etc. You
103installation prefix other than `/usr/local' by giving `configure' the 146can specify an installation prefix other than `/usr/local' by giving
104option `--prefix=PATH'. 147`configure' the option `--prefix=PREFIX', where PREFIX must be an
148absolute file name.
105 149
106 You can specify separate installation prefixes for 150 You can specify separate installation prefixes for
107architecture-specific files and architecture-independent files. If you 151architecture-specific files and architecture-independent files. If you
108give `configure' the option `--exec-prefix=PATH', the package will use 152pass the option `--exec-prefix=PREFIX' to `configure', the package uses
109PATH as the prefix for installing programs and libraries. 153PREFIX as the prefix for installing programs and libraries.
110Documentation and other data files will still use the regular prefix. 154Documentation and other data files still use the regular prefix.
111 155
112 In addition, if you use an unusual directory layout you can give 156 In addition, if you use an unusual directory layout you can give
113options like `--bindir=PATH' to specify different values for particular 157options like `--bindir=DIR' to specify different values for particular
114kinds of files. Run `configure --help' for a list of the directories 158kinds of files. Run `configure --help' for a list of the directories
115you can set and what kinds of files go in them. 159you can set and what kinds of files go in them. In general, the
160default for these options is expressed in terms of `${prefix}', so that
161specifying just `--prefix' will affect all of the other directory
162specifications that were not explicitly provided.
163
164 The most portable way to affect installation locations is to pass the
165correct locations to `configure'; however, many packages provide one or
166both of the following shortcuts of passing variable assignments to the
167`make install' command line to change installation locations without
168having to reconfigure or recompile.
169
170 The first method involves providing an override variable for each
171affected directory. For example, `make install
172prefix=/alternate/directory' will choose an alternate location for all
173directory configuration variables that were expressed in terms of
174`${prefix}'. Any directories that were specified during `configure',
175but not in terms of `${prefix}', must each be overridden at install
176time for the entire installation to be relocated. The approach of
177makefile variable overrides for each directory variable is required by
178the GNU Coding Standards, and ideally causes no recompilation.
179However, some platforms have known limitations with the semantics of
180shared libraries that end up requiring recompilation when using this
181method, particularly noticeable in packages that use GNU Libtool.
182
183 The second method involves providing the `DESTDIR' variable. For
184example, `make install DESTDIR=/alternate/directory' will prepend
185`/alternate/directory' before all installation names. The approach of
186`DESTDIR' overrides is not required by the GNU Coding Standards, and
187does not work on platforms that have drive letters. On the other hand,
188it does better at avoiding recompilation issues, and works well even
189when some directory options were not specified in terms of `${prefix}'
190at `configure' time.
191
192Optional Features
193=================
116 194
117 If the package supports it, you can cause programs to be installed 195 If the package supports it, you can cause programs to be installed
118with an extra prefix or suffix on their names by giving `configure' the 196with an extra prefix or suffix on their names by giving `configure' the
119option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 197option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
120
121Optional Features
122=================
123 198
124 Some packages pay attention to `--enable-FEATURE' options to 199 Some packages pay attention to `--enable-FEATURE' options to
125`configure', where FEATURE indicates an optional part of the package. 200`configure', where FEATURE indicates an optional part of the package.
126They may also pay attention to `--with-PACKAGE' options, where PACKAGE 201They may also pay attention to `--with-PACKAGE' options, where PACKAGE
127is something like `gnu-as' or `x' (for the X Window System). The 202is something like `gnu-as' or `x' (for the X Window System). The
131 For packages that use the X Window System, `configure' can usually 206 For packages that use the X Window System, `configure' can usually
132find the X include and library files automatically, but if it doesn't, 207find the X include and library files automatically, but if it doesn't,
133you can use the `configure' options `--x-includes=DIR' and 208you can use the `configure' options `--x-includes=DIR' and
134`--x-libraries=DIR' to specify their locations. 209`--x-libraries=DIR' to specify their locations.
135 210
211 Some packages offer the ability to configure how verbose the
212execution of `make' will be. For these packages, running `./configure
213--enable-silent-rules' sets the default to minimal output, which can be
214overridden with `make V=1'; while running `./configure
215--disable-silent-rules' sets the default to verbose, which can be
216overridden with `make V=0'.
217
218Particular systems
219==================
220
221 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
222CC is not installed, it is recommended to use the following options in
223order to use an ANSI C compiler:
224
225 ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
226
227and if that doesn't work, install pre-built binaries of GCC for HP-UX.
228
229 HP-UX `make' updates targets which have the same time stamps as
230their prerequisites, which makes it generally unusable when shipped
231generated files such as `configure' are involved. Use GNU `make'
232instead.
233
234 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
235parse its `<wchar.h>' header file. The option `-nodtk' can be used as
236a workaround. If GNU CC is not installed, it is therefore recommended
237to try
238
239 ./configure CC="cc"
240
241and if that doesn't work, try
242
243 ./configure CC="cc -nodtk"
244
245 On Solaris, don't put `/usr/ucb' early in your `PATH'. This
246directory contains several dysfunctional programs; working variants of
247these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
248in your `PATH', put it _after_ `/usr/bin'.
249
250 On Haiku, software installed for all users goes in `/boot/common',
251not `/usr/local'. It is recommended to use the following options:
252
253 ./configure --prefix=/boot/common
254
136Specifying the System Type 255Specifying the System Type
137========================== 256==========================
138 257
139 There may be some features `configure' cannot figure out 258 There may be some features `configure' cannot figure out
140automatically, but needs to determine by the type of host the package 259automatically, but needs to determine by the type of machine the package
141will run on. Usually `configure' can figure that out, but if it prints 260will run on. Usually, assuming the package is built to be run on the
261_same_ architectures, `configure' can figure that out, but if it prints
142a message saying it cannot guess the host type, give it the 262a message saying it cannot guess the machine type, give it the
143`--build=TYPE' option. TYPE can either be a short name for the system 263`--build=TYPE' option. TYPE can either be a short name for the system
144type, such as `sun4', or a canonical name which has the form: 264type, such as `sun4', or a canonical name which has the form:
145 265
146 CPU-COMPANY-SYSTEM 266 CPU-COMPANY-SYSTEM
147 267
148where SYSTEM can have one of these forms: 268where SYSTEM can have one of these forms:
149 269
270 OS
150 OS KERNEL-OS 271 KERNEL-OS
151 272
152 See the file `config.sub' for the possible values of each field. If 273 See the file `config.sub' for the possible values of each field. If
153`config.sub' isn't included in this package, then this package doesn't 274`config.sub' isn't included in this package, then this package doesn't
154need to know the host type. 275need to know the machine type.
155 276
156 If you are _building_ compiler tools for cross-compiling, you should 277 If you are _building_ compiler tools for cross-compiling, you should
157use the `--target=TYPE' option to select the type of system they will 278use the option `--target=TYPE' to select the type of system they will
158produce code for. 279produce code for.
159 280
160 If you want to _use_ a cross compiler, that generates code for a 281 If you want to _use_ a cross compiler, that generates code for a
161platform different from the build platform, you should specify the host 282platform different from the build platform, you should specify the
162platform (i.e., that on which the generated programs will eventually be 283"host" platform (i.e., that on which the generated programs will
163run) with `--host=TYPE'. In this case, you should also specify the 284eventually be run) with `--host=TYPE'.
164build platform with `--build=TYPE', because, in this case, it may not
165be possible to guess the build platform (it sometimes involves
166compiling and running simple test programs, and this can't be done if
167the compiler is a cross compiler).
168 285
169Sharing Defaults 286Sharing Defaults
170================ 287================
171 288
172 If you want to set default values for `configure' scripts to share, 289 If you want to set default values for `configure' scripts to share,
186variables may be lost. In order to avoid this problem, you should set 303variables may be lost. In order to avoid this problem, you should set
187them in the `configure' command line, using `VAR=value'. For example: 304them in the `configure' command line, using `VAR=value'. For example:
188 305
189 ./configure CC=/usr/local2/bin/gcc 306 ./configure CC=/usr/local2/bin/gcc
190 307
191will cause the specified gcc to be used as the C compiler (unless it is 308causes the specified `gcc' to be used as the C compiler (unless it is
192overridden in the site shell script). 309overridden in the site shell script).
310
311Unfortunately, this technique does not work for `CONFIG_SHELL' due to
312an Autoconf bug. Until the bug is fixed you can use this workaround:
313
314 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
193 315
194`configure' Invocation 316`configure' Invocation
195====================== 317======================
196 318
197 `configure' recognizes the following options to control how it 319 `configure' recognizes the following options to control how it
198operates. 320operates.
199 321
200`--help' 322`--help'
201`-h' 323`-h'
202 Print a summary of the options to `configure', and exit. 324 Print a summary of all of the options to `configure', and exit.
325
326`--help=short'
327`--help=recursive'
328 Print a summary of the options unique to this package's
329 `configure', and exit. The `short' variant lists options used
330 only in the top level, while the `recursive' variant lists options
331 also present in any nested packages.
203 332
204`--version' 333`--version'
205`-V' 334`-V'
206 Print the version of Autoconf used to generate the `configure' 335 Print the version of Autoconf used to generate the `configure'
207 script, and exit. 336 script, and exit.
224 353
225`--srcdir=DIR' 354`--srcdir=DIR'
226 Look for the package's source code in directory DIR. Usually 355 Look for the package's source code in directory DIR. Usually
227 `configure' can determine that directory automatically. 356 `configure' can determine that directory automatically.
228 357
358`--prefix=DIR'
359 Use DIR as the installation prefix. *note Installation Names::
360 for more details, including other options available for fine-tuning
361 the installation locations.
362
363`--no-create'
364`-n'
365 Run the configure checks, but stop before creating any output
366 files.
367
229`configure' also accepts some other, not widely useful, options. Run 368`configure' also accepts some other, not widely useful, options. Run
230`configure --help' for more details. 369`configure --help' for more details.
231 370

Legend:
Removed from v.147  
changed lines
  Added in v.346

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