Installing the various components of the GNU Build System can be
autopoint for Gettext,
Makefile.in 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 configure.ac have
been updated, or finally, simply in order to install the GNU Build
System in a fresh tree.
autopoint (when appropriate) repeatedly
to update the GNU Build System in the specified directories and their
subdirectories (see Subdirectories). By default, it only remakes
those files that are older than their sources. The environment variables
MAKE may be used to override the invocation of the respective tools.
If you install a new version of some tool, you can make
autoreconf remake all of the files by giving it the
See Automatic Remaking, for Make rules to automatically
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
Gettext supplies the
autopoint command to add translation
infrastructure to a source package. If you use
your configure.ac should invoke
See Invoking the
autopoint Program in GNU
gettext utilities, for further details.
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
autoreconf examines and the
commands it runs. If given two or more times, pass --verbose
to subordinate tools that support it.
Don’t remove the temporary files.
Consider all generated and standard auxiliary files to be obsolete. This remakes even configure scripts and configuration headers that are newer than their input files (configure.ac and, if present, aclocal.m4).
If deemed appropriate, this option triggers calls to ‘automake
--force-missing’. Passing both --force and --install
autoreconf will in turn undo any customizations to standard
files. Note that the macro
AM_INIT_AUTOMAKE has some options
which change the set of files considered to be standard.
Install any missing standard auxiliary files in the package. By default, files are copied; this can be changed with --symlink.
If deemed appropriate, this option triggers calls to ‘automake --add-missing’, ‘libtoolize’, ‘autopoint’, etc.
Do not rebuild files in subdirectories to configure (see Subdirectories,
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’.
Append dir to the include path. Multiple invocations accumulate.
Passed on to
Prepend dir to the include path. Multiple invocations accumulate.
Passed on to
Enable or disable warnings related to each category. See m4_warn, for a comprehensive list of categories. Special values include:
Enable all categories of warnings.
Disable all categories of warnings.
Treat all warnings as errors.
Disable warnings falling into category.
The enviroment variable
WARNINGS may also be set to a
comma-separated list of warning categories to enable or disable.
It is interpreted exactly the same way as the argument of
--warnings, but unknown categories are silently ignored.
The command line takes precedence; for instance, if
is set to
obsolete, but -Wnone is given on the
command line, no warnings will be issued.
Some categories of warnings are on by default. Again, for details see m4_warn.
If you want
autoreconf to pass flags that are not listed here
ACLOCAL_AMFLAGS in your Makefile.am.
Due to a limitation in the Autoconf implementation these flags currently
must be set on a single line in Makefile.am, without any
backslash-newlines. Also, be aware that future Automake releases might
ACLOCAL_AMFLAGS as obsolescent, or even remove
support for it.