1.1 --- a/gmyth/INSTALL Wed Sep 20 23:45:35 2006 +0100
1.2 +++ b/gmyth/INSTALL Wed Apr 04 18:05:44 2007 +0100
1.3 @@ -1,3 +1,9 @@
1.4 +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
1.5 +Foundation, Inc.
1.6 +
1.7 + This file is free documentation; the Free Software Foundation gives
1.8 +unlimited permission to copy, distribute and modify it.
1.9 +
1.10 Basic Installation
1.11 ==================
1.12
1.13 @@ -8,20 +14,27 @@
1.14 those values to create a `Makefile' in each directory of the package.
1.15 It may also create one or more `.h' files containing system-dependent
1.16 definitions. Finally, it creates a shell script `config.status' that
1.17 -you can run in the future to recreate the current configuration, a file
1.18 -`config.cache' that saves the results of its tests to speed up
1.19 -reconfiguring, and a file `config.log' containing compiler output
1.20 -(useful mainly for debugging `configure').
1.21 +you can run in the future to recreate the current configuration, and a
1.22 +file `config.log' containing compiler output (useful mainly for
1.23 +debugging `configure').
1.24 +
1.25 + It can also use an optional file (typically called `config.cache'
1.26 +and enabled with `--cache-file=config.cache' or simply `-C') that saves
1.27 +the results of its tests to speed up reconfiguring. (Caching is
1.28 +disabled by default to prevent problems with accidental use of stale
1.29 +cache files.)
1.30
1.31 If you need to do unusual things to compile the package, please try
1.32 to figure out how `configure' could check whether to do them, and mail
1.33 diffs or instructions to the address given in the `README' so they can
1.34 -be considered for the next release. If at some point `config.cache'
1.35 -contains results you don't want to keep, you may remove or edit it.
1.36 +be considered for the next release. If you are using the cache, and at
1.37 +some point `config.cache' contains results you don't want to keep, you
1.38 +may remove or edit it.
1.39
1.40 - The file `configure.in' is used to create `configure' by a program
1.41 -called `autoconf'. You only need `configure.in' if you want to change
1.42 -it or regenerate `configure' using a newer version of `autoconf'.
1.43 + The file `configure.ac' (or `configure.in') is used to create
1.44 +`configure' by a program called `autoconf'. You only need
1.45 +`configure.ac' if you want to change it or regenerate `configure' using
1.46 +a newer version of `autoconf'.
1.47
1.48 The simplest way to compile this package is:
1.49
1.50 @@ -55,14 +68,16 @@
1.51 =====================
1.52
1.53 Some systems require unusual options for compilation or linking that
1.54 -the `configure' script does not know about. You can give `configure'
1.55 -initial values for variables by setting them in the environment. Using
1.56 -a Bourne-compatible shell, you can do that on the command line like
1.57 -this:
1.58 - CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
1.59 +the `configure' script does not know about. Run `./configure --help'
1.60 +for details on some of the pertinent environment variables.
1.61
1.62 -Or on systems that have the `env' program, you can do it like this:
1.63 - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
1.64 + You can give `configure' initial values for configuration parameters
1.65 +by setting variables in the command line or in the environment. Here
1.66 +is an example:
1.67 +
1.68 + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
1.69 +
1.70 + *Note Defining Variables::, for more details.
1.71
1.72 Compiling For Multiple Architectures
1.73 ====================================
1.74 @@ -75,11 +90,11 @@
1.75 the `configure' script. `configure' automatically checks for the
1.76 source code in the directory that `configure' is in and in `..'.
1.77
1.78 - If you have to use a `make' that does not supports the `VPATH'
1.79 -variable, you have to compile the package for one architecture at a time
1.80 -in the source code directory. After you have installed the package for
1.81 -one architecture, use `make distclean' before reconfiguring for another
1.82 -architecture.
1.83 + If you have to use a `make' that does not support the `VPATH'
1.84 +variable, you have to compile the package for one architecture at a
1.85 +time in the source code directory. After you have installed the
1.86 +package for one architecture, use `make distclean' before reconfiguring
1.87 +for another architecture.
1.88
1.89 Installation Names
1.90 ==================
1.91 @@ -122,22 +137,32 @@
1.92 Specifying the System Type
1.93 ==========================
1.94
1.95 - There may be some features `configure' can not figure out
1.96 -automatically, but needs to determine by the type of host the package
1.97 -will run on. Usually `configure' can figure that out, but if it prints
1.98 -a message saying it can not guess the host type, give it the
1.99 -`--host=TYPE' option. TYPE can either be a short name for the system
1.100 -type, such as `sun4', or a canonical name with three fields:
1.101 + There may be some features `configure' cannot figure out
1.102 +automatically, but needs to determine by the type of machine the package
1.103 +will run on. Usually, assuming the package is built to be run on the
1.104 +_same_ architectures, `configure' can figure that out, but if it prints
1.105 +a message saying it cannot guess the machine type, give it the
1.106 +`--build=TYPE' option. TYPE can either be a short name for the system
1.107 +type, such as `sun4', or a canonical name which has the form:
1.108 +
1.109 CPU-COMPANY-SYSTEM
1.110
1.111 -See the file `config.sub' for the possible values of each field. If
1.112 +where SYSTEM can have one of these forms:
1.113 +
1.114 + OS KERNEL-OS
1.115 +
1.116 + See the file `config.sub' for the possible values of each field. If
1.117 `config.sub' isn't included in this package, then this package doesn't
1.118 -need to know the host type.
1.119 +need to know the machine type.
1.120
1.121 - If you are building compiler tools for cross-compiling, you can also
1.122 + If you are _building_ compiler tools for cross-compiling, you should
1.123 use the `--target=TYPE' option to select the type of system they will
1.124 -produce code for and the `--build=TYPE' option to select the type of
1.125 -system on which you are compiling the package.
1.126 +produce code for.
1.127 +
1.128 + If you want to _use_ a cross compiler, that generates code for a
1.129 +platform different from the build platform, you should specify the
1.130 +"host" platform (i.e., that on which the generated programs will
1.131 +eventually be run) with `--host=TYPE'.
1.132
1.133 Sharing Defaults
1.134 ================
1.135 @@ -150,19 +175,43 @@
1.136 `CONFIG_SITE' environment variable to the location of the site script.
1.137 A warning: not all `configure' scripts look for a site script.
1.138
1.139 -Operation Controls
1.140 +Defining Variables
1.141 ==================
1.142
1.143 + Variables not defined in a site shell script can be set in the
1.144 +environment passed to `configure'. However, some packages may run
1.145 +configure again during the build, and the customized values of these
1.146 +variables may be lost. In order to avoid this problem, you should set
1.147 +them in the `configure' command line, using `VAR=value'. For example:
1.148 +
1.149 + ./configure CC=/usr/local2/bin/gcc
1.150 +
1.151 +will cause the specified gcc to be used as the C compiler (unless it is
1.152 +overridden in the site shell script).
1.153 +
1.154 +`configure' Invocation
1.155 +======================
1.156 +
1.157 `configure' recognizes the following options to control how it
1.158 operates.
1.159
1.160 +`--help'
1.161 +`-h'
1.162 + Print a summary of the options to `configure', and exit.
1.163 +
1.164 +`--version'
1.165 +`-V'
1.166 + Print the version of Autoconf used to generate the `configure'
1.167 + script, and exit.
1.168 +
1.169 `--cache-file=FILE'
1.170 - Use and save the results of the tests in FILE instead of
1.171 - `./config.cache'. Set FILE to `/dev/null' to disable caching, for
1.172 - debugging `configure'.
1.173 + Enable the cache: use and save the results of the tests in FILE,
1.174 + traditionally `config.cache'. FILE defaults to `/dev/null' to
1.175 + disable caching.
1.176
1.177 -`--help'
1.178 - Print a summary of the options to `configure', and exit.
1.179 +`--config-cache'
1.180 +`-C'
1.181 + Alias for `--cache-file=config.cache'.
1.182
1.183 `--quiet'
1.184 `--silent'
1.185 @@ -175,8 +224,6 @@
1.186 Look for the package's source code in directory DIR. Usually
1.187 `configure' can determine that directory automatically.
1.188
1.189 -`--version'
1.190 - Print the version of Autoconf used to generate the `configure'
1.191 - script, and exit.
1.192 +`configure' also accepts some other, not widely useful, options. Run
1.193 +`configure --help' for more details.
1.194
1.195 -`configure' also accepts some other, not widely useful, options.