NAME

autoreconf - Update generated configuration files

SYNOPSIS

autoreconf [ OPTION] ... [TEMPLATE-FILE]

DESCRIPTION

Run `autoconf' (and `autoheader', `aclocal' and `automake', where appropriate) repeatedly to remake the Autoconf `configure' scripts and configuration header templates in the directory tree rooted at the current directory. By default, it only remakes those files that are older than their predecessors. If you install a new version of Autoconf, running `autoreconf' remakes all of the files by giving it the `--force' option.

Operation modes:

-h, --help
print this help, then exit
-V, --version
print version number, then exit
-v, --verbose
verbosely report processing
-d, --debug
don't remove temporary files
-f, --force
consider every files are obsolete
-i, --install
copy missing auxiliary files
-s, --symlink
instead of copying, install symbolic links
The option `--install' is similar to the option `--add-missing' in other tools.

Library directories:

-A, --autoconf-dir=ACDIR
Autoconf's macro files location (rarely needed)
-l, --localdir=DIR
location of `aclocal.m4' and `acconfig.h'
-M, --m4dir=M4DIR
this package's Autoconf extensions
Unless specified, heuristics try to compute `M4DIR' from the `Makefile.am', or defaults to `m4' if it exists.

The following options are passed to `automake':

--cygnus
assume program is part of Cygnus-style tree
--foreign
set strictness to foreign
--gnits
set strictness to gnits
--gnu
set strictness to gnu
--include-deps
include generated dependencies in Makefile.in
The environment variables AUTOCONF, AUTOHEADER, AUTOMAKE, and ACLOCAL are honored.

AUTHOR

Written by David J. MacKenzie.

REPORTING BUGS

Report bugs to <[email protected]>. Copyright 1994, 1999, 2000 Free Software Foundation, Inc.
 
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

SEE ALSO

autoconf(1), automake(1), autoreconf(1), autoupdate(1), autoheader(1), autoscan(1), config.guess(1), config.sub(1), ifnames(1), libtool(1).
The full documentation for autoreconf is maintained as a Texinfo manual. If the info and autoreconf programs are properly installed at your site, the command
info autoreconf
should give you access to the complete manual.

Recommended readings

Pages related to autoreconf-dickey you should read also:

Questions & Answers

Helpful answers and articles about autoreconf-dickey you may found on these sites:
Stack Overflow Server Fault Super User Unix & Linux Ask Ubuntu Network Engineering DevOps Raspberry Pi Webmasters Google Search