Lines Matching full:for

17 more-detailed instructions are generic; see the `README' file for
21 necessarily a bug.  More recommendations for GNU packages can be found
24    The `configure' shell script attempts to guess correct values for
30 file `config.log' containing compiler output (useful mainly for
42 be considered for the next release.  If you are using the cache, and at
54      `./configure' to configure the package for your system.
57      some messages telling which features it is checking for.
79      files that `configure' created (so you can compile the package for
82      for the package's developers.  If you use it, you may have to get
99    Some systems require unusual options for compilation or linking that
101 for details on some of the pertinent environment variables.
103    You can give `configure' initial values for configuration parameters
109    *Note Defining Variables::, for more details.
111 Compiling For Multiple Architectures
114    You can compile the package for more than one kind of computer at the
115 same time, by placing the object files for each architecture in their
118 the `configure' script.  `configure' automatically checks for the
122    With a non-GNU `make', it is safer to compile the package for one
124 installed the package for one architecture, use `make distclean' before
125 reconfiguring for another architecture.
150    You can specify separate installation prefixes for
153 PREFIX as the prefix for installing programs and libraries.
157 options like `--bindir=DIR' to specify different values for particular
158 kinds of files.  Run `configure --help' for a list of the directories
160 default for these options is expressed in terms of `${prefix}', so that
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
176 time for the entire installation to be relocated.  The approach of
177 makefile variable overrides for each directory variable is required by
183    The second method involves providing the `DESTDIR' variable.  For
202 is something like `gnu-as' or `x' (for the X Window System).  The
206    For packages that use the X Window System, `configure' can usually
212 execution of `make' will be.  For these packages, running `./configure
227 and if that doesn't work, install pre-built binaries of GCC for HP-UX.
245    On Haiku, software installed for all users goes in `/boot/common',
258 `--build=TYPE' option.  TYPE can either be a short name for the system
268    See the file `config.sub' for the possible values of each field.  If
272    If you are _building_ compiler tools for cross-compiling, you should
274 produce code for.
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,
286 default values for variables like `CC', `cache_file', and `prefix'.
287 `configure' looks for `PREFIX/share/config.site' if it exists, then
290 A warning: not all `configure' scripts look for a site script.
299 them in the `configure' command line, using `VAR=value'.  For example:
306 Unfortunately, this technique does not work for `CONFIG_SHELL' due to
340      Alias for `--cache-file=config.cache'.
350      Look for the package's source code in directory DIR.  Usually
355      for more details, including other options available for fine-tuning
364 `configure --help' for more details.