Lines Matching full:to
18 instructions specific to this package. Some packages provide this
24 The `configure' shell script attempts to guess correct values for
26 those values to create a `Makefile' in each directory of the package.
29 you can run in the future to recreate the current configuration, and a
35 the results of its tests to speed up reconfiguring. Caching is
36 disabled by default to prevent problems with accidental use of stale
39 If you need to do unusual things to compile the package, please try
40 to figure out how `configure' could check whether to do them, and mail
41 diffs or instructions to the address given in the `README' so they can
43 some point `config.cache' contains results you don't want to keep, you
46 The file `configure.ac' (or `configure.in') is used to create
48 you want to change it or regenerate `configure' using a newer version
51 The simplest way to compile this package is:
53 1. `cd' to the directory containing the package's source code and type
54 `./configure' to configure the package for your system.
59 2. Type `make' to compile the package.
61 3. Optionally, type `make check' to run any self-tests that come with
64 4. Type `make install' to install the programs and any data files and
70 5. Optionally, type `make installcheck' to repeat any self-tests, but
78 source code directory by typing `make clean'. To also remove the
82 for the package's developers. If you use it, you may have to get
83 all sorts of other programs in order to regenerate files that came
86 7. Often, you can also type `make uninstall' to remove the installed
92 distcheck', which can by used by developers to test that all other
116 own directory. To do this, you can use GNU `make'. `cd' to the
117 directory where you want the object files and executables to go and run
122 With a non-GNU `make', it is safer to compile the package for one
129 "universal" binaries--by specifying multiple `-arch' options to the
130 compiler but only a single `-arch' option to the preprocessor. Like
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
152 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
157 options like `--bindir=DIR' to specify different values for particular
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.
176 time for the entire installation to be relocated. The approach of
195 If the package supports it, you can cause programs to be installed
199 Some packages pay attention to `--enable-FEATURE' options to
201 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
209 `--x-libraries=DIR' to specify their locations.
211 Some packages offer the ability to configure how verbose the
213 --enable-silent-rules' sets the default to minimal output, which can be
215 --disable-silent-rules' sets the default to verbose, which can be
222 CC is not installed, it is recommended to use the following options in
223 order to use an ANSI C compiler:
232 to try
246 not `/usr/local'. It is recommended to use the following options:
254 automatically, but needs to determine by the type of machine the package
255 will run on. Usually, assuming the package is built to be run on the
270 need to know the machine type.
273 use the option `--target=TYPE' to select the type of system they will
276 If you want to _use_ a cross compiler, that generates code for a
284 If you want to set default values for `configure' scripts to share,
289 `CONFIG_SITE' environment variable to the location of the site script.
296 environment passed to `configure'. However, some packages may run
298 variables may be lost. In order to avoid this problem, you should set
303 causes the specified `gcc' to be used as the C compiler (unless it is
306 Unfortunately, this technique does not work for `CONFIG_SHELL' due to
314 `configure' recognizes the following options to control how it
319 Print a summary of all of the options to `configure', and exit.
323 Print a summary of the options unique to this package's
330 Print the version of Autoconf used to generate the `configure'
335 traditionally `config.cache'. FILE defaults to `/dev/null' to
345 Do not print messages saying which checks are being made. To
346 suppress all normal output, redirect it to `/dev/null' (any error