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

Diff of /psiconv/trunk/INSTALL

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

Revision 269 Revision 270
1Installation Instructions
2*************************
3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free 1Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
5Software Foundation, Inc. 2Foundation, Inc.
6 3
7This file is free documentation; the Free Software Foundation gives 4 This file is free documentation; the Free Software Foundation gives
8unlimited permission to copy, distribute and modify it. 5unlimited permission to copy, distribute and modify it.
9 6
10Basic Installation 7Basic Installation
11================== 8==================
12 9
13These are generic installation instructions. 10 These are generic installation instructions.
14 11
15 The `configure' shell script attempts to guess correct values for 12 The `configure' shell script attempts to guess correct values for
16various system-dependent variables used during compilation. It uses 13various system-dependent variables used during compilation. It uses
17those values to create a `Makefile' in each directory of the package. 14those values to create a `Makefile' in each directory of the package.
18It may also create one or more `.h' files containing system-dependent 15It may also create one or more `.h' files containing system-dependent
68 with the distribution. 65 with the distribution.
69 66
70Compilers and Options 67Compilers and Options
71===================== 68=====================
72 69
73Some systems require unusual options for compilation or linking that the 70 Some systems require unusual options for compilation or linking that
74`configure' script does not know about. Run `./configure --help' for 71the `configure' script does not know about. Run `./configure --help'
75details on some of the pertinent environment variables. 72for details on some of the pertinent environment variables.
76 73
77 You can give `configure' initial values for configuration parameters 74 You can give `configure' initial values for configuration parameters
78by setting variables in the command line or in the environment. Here 75by setting variables in the command line or in the environment. Here
79is an example: 76is an example:
80 77
83 *Note Defining Variables::, for more details. 80 *Note Defining Variables::, for more details.
84 81
85Compiling For Multiple Architectures 82Compiling For Multiple Architectures
86==================================== 83====================================
87 84
88You can compile the package for more than one kind of computer at the 85 You can compile the package for more than one kind of computer at the
89same time, by placing the object files for each architecture in their 86same time, by placing the object files for each architecture in their
90own directory. To do this, you must use a version of `make' that 87own directory. To do this, you must use a version of `make' that
91supports the `VPATH' variable, such as GNU `make'. `cd' to the 88supports the `VPATH' variable, such as GNU `make'. `cd' to the
92directory where you want the object files and executables to go and run 89directory where you want the object files and executables to go and run
93the `configure' script. `configure' automatically checks for the 90the `configure' script. `configure' automatically checks for the
100for another architecture. 97for another architecture.
101 98
102Installation Names 99Installation Names
103================== 100==================
104 101
105By default, `make install' will install the package's files in 102 By default, `make install' will install the package's files in
106`/usr/local/bin', `/usr/local/man', etc. You can specify an 103`/usr/local/bin', `/usr/local/man', etc. You can specify an
107installation prefix other than `/usr/local' by giving `configure' the 104installation prefix other than `/usr/local' by giving `configure' the
108option `--prefix=PREFIX'. 105option `--prefix=PATH'.
109 106
110 You can specify separate installation prefixes for 107 You can specify separate installation prefixes for
111architecture-specific files and architecture-independent files. If you 108architecture-specific files and architecture-independent files. If you
112give `configure' the option `--exec-prefix=PREFIX', the package will 109give `configure' the option `--exec-prefix=PATH', the package will use
113use PREFIX as the prefix for installing programs and libraries. 110PATH as the prefix for installing programs and libraries.
114Documentation and other data files will still use the regular prefix. 111Documentation and other data files will still use the regular prefix.
115 112
116 In addition, if you use an unusual directory layout you can give 113 In addition, if you use an unusual directory layout you can give
117options like `--bindir=DIR' to specify different values for particular 114options like `--bindir=PATH' to specify different values for particular
118kinds of files. Run `configure --help' for a list of the directories 115kinds of files. Run `configure --help' for a list of the directories
119you can set and what kinds of files go in them. 116you can set and what kinds of files go in them.
120 117
121 If the package supports it, you can cause programs to be installed 118 If the package supports it, you can cause programs to be installed
122with an extra prefix or suffix on their names by giving `configure' the 119with an extra prefix or suffix on their names by giving `configure' the
123option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 120option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
124 121
125Optional Features 122Optional Features
126================= 123=================
127 124
128Some packages pay attention to `--enable-FEATURE' options to 125 Some packages pay attention to `--enable-FEATURE' options to
129`configure', where FEATURE indicates an optional part of the package. 126`configure', where FEATURE indicates an optional part of the package.
130They may also pay attention to `--with-PACKAGE' options, where PACKAGE 127They may also pay attention to `--with-PACKAGE' options, where PACKAGE
131is something like `gnu-as' or `x' (for the X Window System). The 128is something like `gnu-as' or `x' (for the X Window System). The
132`README' should mention any `--enable-' and `--with-' options that the 129`README' should mention any `--enable-' and `--with-' options that the
133package recognizes. 130package recognizes.
138`--x-libraries=DIR' to specify their locations. 135`--x-libraries=DIR' to specify their locations.
139 136
140Specifying the System Type 137Specifying the System Type
141========================== 138==========================
142 139
143There may be some features `configure' cannot figure out automatically, 140 There may be some features `configure' cannot figure out
144but needs to determine by the type of machine the package will run on. 141automatically, but needs to determine by the type of machine the package
145Usually, assuming the package is built to be run on the _same_ 142will run on. Usually, assuming the package is built to be run on the
146architectures, `configure' can figure that out, but if it prints a 143_same_ architectures, `configure' can figure that out, but if it prints
147message saying it cannot guess the machine type, give it the 144a message saying it cannot guess the machine type, give it the
148`--build=TYPE' option. TYPE can either be a short name for the system 145`--build=TYPE' option. TYPE can either be a short name for the system
149type, such as `sun4', or a canonical name which has the form: 146type, such as `sun4', or a canonical name which has the form:
150 147
151 CPU-COMPANY-SYSTEM 148 CPU-COMPANY-SYSTEM
152 149
168eventually be run) with `--host=TYPE'. 165eventually be run) with `--host=TYPE'.
169 166
170Sharing Defaults 167Sharing Defaults
171================ 168================
172 169
173If you want to set default values for `configure' scripts to share, you 170 If you want to set default values for `configure' scripts to share,
174can create a site shell script called `config.site' that gives default 171you can create a site shell script called `config.site' that gives
175values for variables like `CC', `cache_file', and `prefix'. 172default values for variables like `CC', `cache_file', and `prefix'.
176`configure' looks for `PREFIX/share/config.site' if it exists, then 173`configure' looks for `PREFIX/share/config.site' if it exists, then
177`PREFIX/etc/config.site' if it exists. Or, you can set the 174`PREFIX/etc/config.site' if it exists. Or, you can set the
178`CONFIG_SITE' environment variable to the location of the site script. 175`CONFIG_SITE' environment variable to the location of the site script.
179A warning: not all `configure' scripts look for a site script. 176A warning: not all `configure' scripts look for a site script.
180 177
181Defining Variables 178Defining Variables
182================== 179==================
183 180
184Variables not defined in a site shell script can be set in the 181 Variables not defined in a site shell script can be set in the
185environment passed to `configure'. However, some packages may run 182environment passed to `configure'. However, some packages may run
186configure again during the build, and the customized values of these 183configure again during the build, and the customized values of these
187variables may be lost. In order to avoid this problem, you should set 184variables may be lost. In order to avoid this problem, you should set
188them in the `configure' command line, using `VAR=value'. For example: 185them in the `configure' command line, using `VAR=value'. For example:
189 186
193overridden in the site shell script). 190overridden in the site shell script).
194 191
195`configure' Invocation 192`configure' Invocation
196====================== 193======================
197 194
198`configure' recognizes the following options to control how it operates. 195 `configure' recognizes the following options to control how it
196operates.
199 197
200`--help' 198`--help'
201`-h' 199`-h'
202 Print a summary of the options to `configure', and exit. 200 Print a summary of the options to `configure', and exit.
203 201

Legend:
Removed from v.269  
changed lines
  Added in v.270

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