Lines Matching full:configure
3546 `configure'. This script is given arguments which describe the kind of
3549 The `configure' script must record the configuration options so that
3558 Another thing that `configure' can do is to edit the Makefile. If
3564 If `configure' does write the `Makefile', then `Makefile' should
3565 have a target named `Makefile' which causes `configure' to be rerun,
3567 that `configure' reads should be listed as dependencies of `Makefile'.
3569 All the files which are output from the `configure' script should
3571 automatically using `configure'. This is so that users won't think of
3574 The `configure' script should write a file named `config.status'
3579 The `configure' script should accept an option of the form
3585 If the user does not specify `--srcdir', then `configure' should
3594 `configure' can add to the Makefile a variable named `srcdir' whose
3597 The `configure' script should also take an argument which specifies
3606 The `configure' script needs to be able to decode all plausible
3614 The `configure' script should also take the option
3616 argument. For example, `configure --build=i686-pc-linux-gnu' is
3617 equivalent to `configure i686-pc-linux-gnu'. When the build type is
3618 not specified by an option or argument, the `configure' script should
3628 Configure the package to build and install an optional user-level
3640 The package PACKAGE will be installed, so configure this package
3653 process. For example, the user could issue `configure CFLAGS=-g
3657 Specifying variables as arguments to `configure', like this:
3658 ./configure CC=gcc
3660 CC=gcc ./configure
3664 All `configure' scripts should accept all of the "detail" options
3668 will be able to configure an entire GNU source tree at once with a
3681 The `configure' script should normally treat the specified type of
3686 build type, use the configure option `--host=HOSTTYPE', where HOSTTYPE
3690 To configure a cross-compiler, cross-assembler, or what have you, you
3691 should specify a target different from the host, using the configure
3695 ./configure --host=HOSTTYPE --target=TARGETTYPE
3703 your program is set up to do this, your `configure' script can simply
3762 `configure'. A rule of the form:
3814 `configure') to run in `sh', not in `csh'. Don't use any special
3817 The `configure' script and the Makefile rules for building and
3997 (e.g., `make prefix=/usr install' or `configure' (e.g., `configure
4128 should never need to modify files in this directory to configure
4216 your `configure.in' file:
4269 variable is normally inserted by the `configure' shell script.
4470 `make maintainer-clean' should not delete `configure' even if
4471 `configure' can be remade using a rule in the Makefile. More
4473 needs to exist in order to run `configure' and then begin to build
5376 * configure: Configuration. (line 6)
5455 * optional features, configure-time: Configuration. (line 83)
