/[public]/psiconv/trunk/INSTALL

Diff of /psiconv/trunk/INSTALL

Parent Directory | Revision Log | View Patch Patch

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

 Legend:



Removed from v.152
 


changed lines


 
Added in v.340
 Legend:



Removed from v.152
 


changed lines


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

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