/[public]/psiconv/trunk/INSTALL

Diff of /psiconv/trunk/INSTALL

Parent Directory | Revision Log | View Patch Patch

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

 Legend:



Removed from v.150
 


changed lines


 
Added in v.152
 Legend:



Removed from v.150
 


changed lines


 
Added in v.152
-Removed from v.150
+Added in v.152

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