autoreconf Invocation

Go backward to autoconf Invocation
Go up to Making configure Scripts
Go to the top op autoconf

Using `autoreconf' to Update `configure' Scripts

Installing the various components of the GNU Build System can be
tedious: running `autopoint' for Gettext, `automake' for `'
etc. in each directory.  It may be needed either because some tools
such as `automake' have been updated on your system, or because some of
the sources such as `' have been updated, or finally,
simply in order to install the GNU Build System in a fresh tree.
   `autoreconf' runs `autoconf', `autoheader', `aclocal', `automake',
`libtoolize', and `autopoint' (when appropriate) repeatedly to update
the GNU Build System in the specified directories and their
subdirectories (*note Subdirectories::).  By default, it only remakes
those files that are older than their sources.
   If you install a new version of some tool, you can make `autoreconf'
remake _all_ of the files by giving it the `--force' option.
   *Note Automatic Remaking::, for `Makefile' rules to automatically
remake `configure' scripts when their source files change.  That method
handles the timestamps of configuration header templates properly, but
does not pass `--autoconf-dir=DIR' or `--localdir=DIR'.
`autoreconf' accepts the following options:
     Print a summary of the command line options and exit.
     Print the version number of Autoconf and exit.
     Print the name of each directory where `autoreconf' runs
     `autoconf' (and `autoheader', if appropriate).
     Don't remove the temporary files.
     Remake even `configure' scripts and configuration headers that are
     newer than their input files (`' and, if present,
     Install the missing auxiliary files in the package.  By default,
     files are copied; this can be changed with `--symlink'.
     This option triggers calls to `automake --add-missing',
     `libtoolize', `autopoint', etc.
     When used with `--install', install symbolic links to the missing
     auxiliary files instead of copying them.
     When the directories were configured, update the configuration by
     running `./config.status --recheck && ./config.status', and then
     run `make'.
`-I DIR'
     Append DIR to the include path.  Multiple invocations accumulate.
`-B DIR'
     Prepend DIR to the include path.  Multiple invocations accumulate.
     Report the warnings related to CATEGORY (which can actually be a
     comma separated list).
          related to cross compilation issues.
          report the uses of obsolete constructs.
          portability issues
          dubious syntactic constructs.
          report all the warnings
          report none
          treats warnings as errors
          disable warnings falling into CATEGORY
     Warnings about `syntax' are enabled by default, and the environment
     variable `WARNINGS', a comma separated list of categories, is
     honored.  Passing `-W CATEGORY' will actually behave as if you had
     passed `--warnings=syntax,$WARNINGS,CATEGORY'.  If you want to
     disable the defaults and `WARNINGS', but (for example) enable the
     warnings about obsolete constructs, you would use `-W