15818
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 8 ==================
+ ��膩��鰹申鐃順�渇��膩��� 9
+ ��膩��鰹申鐃順�渇��膩��� 10 These are generic installation instructions.
+ ��膩��鰹申鐃順�渇��膩��� 11
+ ��膩��鰹申鐃順�渇��膩��� 12 The `configure' shell script attempts to guess correct values for
+ ��膩��鰹申鐃順�渇��膩��� 13 various system-dependent variables used during compilation. It uses
+ ��膩��鰹申鐃順�渇��膩��� 14 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
+ ��膩��鰹申鐃順�渇��膩��� 16 definitions. Finally, it creates a shell script `config.status' that
+ ��膩��鰹申鐃順�渇��膩��� 17 you can run in the future to recreate the current configuration, and a
+ ��膩��鰹申鐃順�渇��膩��� 18 file `config.log' containing compiler output (useful mainly for
+ ��膩��鰹申鐃順�渇��膩��� 19 debugging `configure').
+ ��膩��鰹申鐃順�渇��膩��� 20
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 27 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
+ ��膩��鰹申鐃順�渇��膩��� 29 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
+ ��膩��鰹申鐃順�渇��膩��� 31 some point `config.cache' contains results you don't want to keep, you
+ ��膩��鰹申鐃順�渇��膩��� 32 may remove or edit it.
+ ��膩��鰹申鐃順�渇��膩��� 33
+ ��膩��鰹申鐃順�渇��膩��� 34 The file `configure.ac' (or `configure.in') is used to create
+ ��膩��鰹申鐃順�渇��膩��� 35 `configure' by a program called `autoconf'. You only need
+ ��膩��鰹申鐃順�渇��膩��� 36 `configure.ac' if you want to change it or regenerate `configure' using
+ ��膩��鰹申鐃順�渇��膩��� 37 a newer version of `autoconf'.
+ ��膩��鰹申鐃順�渇��膩��� 38
+ ��膩��鰹申鐃順�渇��膩��� 39 The simplest way to compile this package is:
+ ��膩��鰹申鐃順�渇��膩��� 40
+ ��膩��鰹申鐃順�渇��膩��� 41 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
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 47 Running `configure' takes awhile. While running, it prints some
+ ��膩��鰹申鐃順�渇��膩��� 48 messages telling which features it is checking for.
+ ��膩��鰹申鐃順�渇��膩��� 49
+ ��膩��鰹申鐃順�渇��膩��� 50 2. Type `make' to compile the package.
+ ��膩��鰹申鐃順�渇��膩��� 51
+ ��膩��鰹申鐃順�渇��膩��� 52 3. Optionally, type `make check' to run any self-tests that come with
+ ��膩��鰹申鐃順�渇��膩��� 53 the package.
+ ��膩��鰹申鐃順�渇��膩��� 54
+ ��膩��鰹申鐃順�渇��膩��� 55 4. Type `make install' to install the programs and any data files and
+ ��膩��鰹申鐃順�渇��膩��� 56 documentation.
+ ��膩��鰹申鐃順�渇��膩��� 57
+ ��膩��鰹申鐃順�渇��膩��� 58 5. You can remove the program binaries and object files from the
+ ��膩��鰹申鐃順�渇��膩��� 59 source code directory by typing `make clean'. To also remove the
+ ��膩��鰹申鐃順�渇��膩��� 60 files that `configure' created (so you can compile the package for
+ ��膩��鰹申鐃順�渇��膩��� 61 a different kind of computer), type `make distclean'. There is
+ ��膩��鰹申鐃順�渇��膩��� 62 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
+ ��膩��鰹申鐃順�渇��膩��� 64 all sorts of other programs in order to regenerate files that came
+ ��膩��鰹申鐃順�渇��膩��� 65 with the distribution.
+ ��膩��鰹申鐃順�渇��膩��� 66
+ ��膩��鰹申鐃順�渇��膩��� 67 Compilers and Options
+ ��膩��鰹申鐃順�渇��膩��� 68 =====================
+ ��膩��鰹申鐃順�渇��膩��� 69
+ ��膩��鰹申鐃順�渇��膩��� 70 Some systems require unusual options for compilation or linking that
+ ��膩��鰹申鐃順�渇��膩��� 71 the `configure' script does not know about. Run `./configure --help'
+ ��膩��鰹申鐃順�渇��膩��� 72 for details on some of the pertinent environment variables.
+ ��膩��鰹申鐃順�渇��膩��� 73
+ ��膩��鰹申鐃順�渇��膩��� 74 You can give `configure' initial values for configuration parameters
+ ��膩��鰹申鐃順�渇��膩��� 75 by setting variables in the command line or in the environment. Here
+ ��膩��鰹申鐃順�渇��膩��� 76 is an example:
+ ��膩��鰹申鐃順�渇��膩��� 77
+ ��膩��鰹申鐃順�渇��膩��� 78 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+ ��膩��鰹申鐃順�渇��膩��� 79
+ ��膩��鰹申鐃順�渇��膩��� 80 *Note Defining Variables::, for more details.
+ ��膩��鰹申鐃順�渇��膩��� 81
+ ��膩��鰹申鐃順�渇��膩��� 82 Compiling For Multiple Architectures
+ ��膩��鰹申鐃順�渇��膩��� 83 ====================================
+ ��膩��鰹申鐃順�渇��膩��� 84
+ ��膩��鰹申鐃順�渇��膩��� 85 You can compile the package for more than one kind of computer at the
+ ��膩��鰹申鐃順�渇��膩��� 86 same time, by placing the object files for each architecture in their
+ ��膩��鰹申鐃順�渇��膩��� 87 own directory. To do this, you must use a version of `make' that
+ ��膩��鰹申鐃順�渇��膩��� 88 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
+ ��膩��鰹申鐃順�渇��膩��� 90 the `configure' script. `configure' automatically checks for the
+ ��膩��鰹申鐃順�渇��膩��� 91 source code in the directory that `configure' is in and in `..'.
+ ��膩��鰹申鐃順�渇��膩��� 92
+ ��膩��鰹申鐃順�渇��膩��� 93 If you have to use a `make' that does not support the `VPATH'
+ ��膩��鰹申鐃順�渇��膩��� 94 variable, you have to compile the package for one architecture at a
+ ��膩��鰹申鐃順�渇��膩��� 95 time in the source code directory. After you have installed the
+ ��膩��鰹申鐃順�渇��膩��� 96 package for one architecture, use `make distclean' before reconfiguring
+ ��膩��鰹申鐃順�渇��膩��� 97 for another architecture.
+ ��膩��鰹申鐃順�渇��膩��� 98
+ ��膩��鰹申鐃順�渇��膩��� 99 Installation Names
+ ��膩��鰹申鐃順�渇��膩��� 100 ==================
+ ��膩��鰹申鐃順�渇��膩��� 101
+ ��膩��鰹申鐃順�渇��膩��� 102 By default, `make install' will install the package's files in
+ ��膩��鰹申鐃順�渇��膩��� 103 `/usr/local/bin', `/usr/local/man', etc. You can specify an
+ ��膩��鰹申鐃順�渇��膩��� 104 installation prefix other than `/usr/local' by giving `configure' the
+ ��膩��鰹申鐃順�渇��膩��� 105 option `--prefix=PATH'.
+ ��膩��鰹申鐃順�渇��膩��� 106
+ ��膩��鰹申鐃順�渇��膩��� 107 You can specify separate installation prefixes for
+ ��膩��鰹申鐃順�渇��膩��� 108 architecture-specific files and architecture-independent files. If you
+ ��膩��鰹申鐃順�渇��膩��� 109 give `configure' the option `--exec-prefix=PATH', the package will use
+ ��膩��鰹申鐃順�渇��膩��� 110 PATH as the prefix for installing programs and libraries.
+ ��膩��鰹申鐃順�渇��膩��� 111 Documentation and other data files will still use the regular prefix.
+ ��膩��鰹申鐃順�渇��膩��� 112
+ ��膩��鰹申鐃順�渇��膩��� 113 In addition, if you use an unusual directory layout you can give
+ ��膩��鰹申鐃順�渇��膩��� 114 options like `--bindir=PATH' to specify different values for particular
+ ��膩��鰹申鐃順�渇��膩��� 115 kinds of files. Run `configure --help' for a list of the directories
+ ��膩��鰹申鐃順�渇��膩��� 116 you can set and what kinds of files go in them.
+ ��膩��鰹申鐃順�渇��膩��� 117
+ ��膩��鰹申鐃順�渇��膩��� 118 If the package supports it, you can cause programs to be installed
+ ��膩��鰹申鐃順�渇��膩��� 119 with an extra prefix or suffix on their names by giving `configure' the
+ ��膩��鰹申鐃順�渇��膩��� 120 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+ ��膩��鰹申鐃順�渇��膩��� 121
+ ��膩��鰹申鐃順�渇��膩��� 122 Optional Features
+ ��膩��鰹申鐃順�渇��膩��� 123 =================
+ ��膩��鰹申鐃順�渇��膩��� 124
+ ��膩��鰹申鐃順�渇��膩��� 125 Some packages pay attention to `--enable-FEATURE' options to
+ ��膩��鰹申鐃順�渇��膩��� 126 `configure', where FEATURE indicates an optional part of the package.
+ ��膩��鰹申鐃順�渇��膩��� 127 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+ ��膩��鰹申鐃順�渇��膩��� 128 is something like `gnu-as' or `x' (for the X Window System). The
+ ��膩��鰹申鐃順�渇��膩��� 129 `README' should mention any `--enable-' and `--with-' options that the
+ ��膩��鰹申鐃順�渇��膩��� 130 package recognizes.
+ ��膩��鰹申鐃順�渇��膩��� 131
+ ��膩��鰹申鐃順�渇��膩��� 132 For packages that use the X Window System, `configure' can usually
+ ��膩��鰹申鐃順�渇��膩��� 133 find the X include and library files automatically, but if it doesn't,
+ ��膩��鰹申鐃順�渇��膩��� 134 you can use the `configure' options `--x-includes=DIR' and
+ ��膩��鰹申鐃順�渇��膩��� 135 `--x-libraries=DIR' to specify their locations.
+ ��膩��鰹申鐃順�渇��膩��� 136
+ ��膩��鰹申鐃順�渇��膩��� 137 Specifying the System Type
+ ��膩��鰹申鐃順�渇��膩��� 138 ==========================
+ ��膩��鰹申鐃順�渇��膩��� 139
+ ��膩��鰹申鐃順�渇��膩��� 140 There may be some features `configure' cannot figure out
+ ��膩��鰹申鐃順�渇��膩��� 141 automatically, but needs to determine by the type of machine the package
+ ��膩��鰹申鐃順�渇��膩��� 142 will run on. Usually, assuming the package is built to be run on the
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 145 `--build=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:
+ ��膩��鰹申鐃順�渇��膩��� 147
+ ��膩��鰹申鐃順�渇��膩��� 148 CPU-COMPANY-SYSTEM
+ ��膩��鰹申鐃順�渇��膩��� 149
+ ��膩��鰹申鐃順�渇��膩��� 150 where SYSTEM can have one of these forms:
+ ��膩��鰹申鐃順�渇��膩��� 151
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 159 use the `--target=TYPE' option to select the type of system they will
+ ��膩��鰹申鐃順�渇��膩��� 160 produce code for.
+ ��膩��鰹申鐃順�渇��膩��� 161
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 167 Sharing Defaults
+ ��膩��鰹申鐃順�渇��膩��� 168 ================
+ ��膩��鰹申鐃順�渇��膩��� 169
+ ��膩��鰹申鐃順�渇��膩��� 170 If you want to set default values for `configure' scripts to share,
+ ��膩��鰹申鐃順�渇��膩��� 171 you can create a site shell script called `config.site' that gives
+ ��膩��鰹申鐃順�渇��膩��� 172 default values for variables like `CC', `cache_file', and `prefix'.
+ ��膩��鰹申鐃順�渇��膩��� 173 `configure' looks for `PREFIX/share/config.site' if it exists, then
+ ��膩��鰹申鐃順�渇��膩��� 174 `PREFIX/etc/config.site' if it exists. Or, you can set the
+ ��膩��鰹申鐃順�渇��膩��� 175 `CONFIG_SITE' environment variable to the location of the site script.
+ ��膩��鰹申鐃順�渇��膩��� 176 A warning: not all `configure' scripts look for a site script.
+ ��膩��鰹申鐃順�渇��膩��� 177
+ ��膩��鰹申鐃順�渇��膩��� 178 Defining Variables
+ ��膩��鰹申鐃順�渇��膩��� 179 ==================
+ ��膩��鰹申鐃順�渇��膩��� 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
+ ��膩��鰹申鐃順�渇��膩��� 195 `configure' recognizes the following options to control how it
+ ��膩��鰹申鐃順�渇��膩��� 196 operates.
+ ��膩��鰹申鐃順�渇��膩��� 197
+ ��膩��鰹申鐃順�渇��膩��� 198 `--help'
+ ��膩��鰹申鐃順�渇��膩��� 199 `-h'
+ ��膩��鰹申鐃順�渇��膩��� 200 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
+ ��膩��鰹申鐃順�渇��膩��� 216 `--quiet'
+ ��膩��鰹申鐃順�渇��膩��� 217 `--silent'
+ ��膩��鰹申鐃順�渇��膩��� 218 `-q'
+ ��膩��鰹申鐃順�渇��膩��� 219 Do not print messages saying which checks are being made. To
+ ��膩��鰹申鐃順�渇��膩��� 220 suppress all normal output, redirect it to `/dev/null' (any error
+ ��膩��鰹申鐃順�渇��膩��� 221 messages will still be shown).
+ ��膩��鰹申鐃順�渇��膩��� 222
+ ��膩��鰹申鐃順�渇��膩��� 223 `--srcdir=DIR'
+ ��膩��鰹申鐃順�渇��膩��� 224 Look for the package's source code in directory DIR. Usually
+ ��膩��鰹申鐃順�渇��膩��� 225 `configure' can determine that directory automatically.
+ ��膩��鰹申鐃順�渇��膩��� 226
+ ��膩��鰹申鐃順�渇��膩��� 227 `configure' also accepts some other, not widely useful, options. Run
+ ��膩��鰹申鐃順�渇��膩��� 228 `configure --help' for more details.
+ ��膩��鰹申鐃順�渇��膩��� 229