Lines Matching refs:in

8 are permitted in any medium without royalty provided the copyright
20 below.  The lack of an optional feature in a given package is not
22 in *note Makefile Conventions: (standards)Makefile Conventions.
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
41 diffs or instructions to the address given in the `README' so they can
46    The file `configure.ac' (or `configure.in') is used to create
71      this time using the binaries in their final installed location.
83      all sorts of other programs in order to regenerate files that came
104 by setting variables in the command line or in the environment.  Here
115 same time, by placing the object files for each architecture in their
119 source code in the directory that `configure' is in and in `..'.  This
123 architecture at a time in the source code directory.  After you have
137    This is not guaranteed to produce working output in all cases, you
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
173 directory configuration variables that were expressed in terms of
175 but not in terms of `${prefix}', must each be overridden at install
181 method, particularly noticeable in packages that use GNU Libtool.
189 when some directory options were not specified in terms of `${prefix}'
222 CC is not installed, it is recommended to use the following options in
245    On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
247 these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
248 in your `PATH', put it _after_ `/usr/bin'.
250    On Haiku, software installed for all users goes in `/boot/common',
274 `config.sub' isn't included in this package, then this package doesn't
300    Variables not defined in a site shell script can be set in the
304 them in the `configure' command line, using `VAR=value'.  For example:
309 overridden in the site shell script).
330      only in the top level, while the `recursive' variant lists options
331      also present in any nested packages.
339      Enable the cache: use and save the results of the tests in FILE,
355      Look for the package's source code in directory DIR.  Usually