---- autoconf-2.54/doc/autoconf.texi.wiget Fri Oct 18 10:53:27 2002
-+++ autoconf-2.54/doc/autoconf.texi Fri Oct 18 11:01:49 2002
-@@ -94,33 +94,19 @@
+diff -Nur autoconf-2.56.orig/doc/autoconf.texi autoconf-2.56/doc/autoconf.texi
+--- autoconf-2.56.orig/doc/autoconf.texi Mon Nov 18 21:47:10 2002
++++ autoconf-2.56/doc/autoconf.texi Mon Nov 18 21:52:44 2002
+@@ -95,33 +95,19 @@
- Remaking multiple @command{configure} scripts
-* autoheader: (autoconf)autoheader Invocation.
- How to create configuration templates
--* autom4te: (autoconf)Invoking autom4te.
+-* autom4te: (autoconf)autom4te Invocation.
- The Autoconf executables backbone
-* configure: (autoconf)configure Invocation.
- Configuring a package
@end direntry
@titlepage
-@@ -160,7 +146,7 @@
+@@ -161,7 +147,7 @@
* Manual Configuration:: Selecting features that can't be guessed
* Site Configuration:: Local defaults for @command{configure}
* Running configure Scripts:: How to use the Autoconf output
* Obsolete Constructs:: Kept for backward compatibility
* Using Autotest:: Creating portable test suites
* FAQ:: Frequent Autoconf Questions, with answers
-@@ -180,10 +166,10 @@
+@@ -181,10 +167,10 @@
Making @command{configure} Scripts
* Writing configure.ac:: What to put in an Autoconf input file
Writing @file{configure.ac}
-@@ -216,7 +202,7 @@
+@@ -217,7 +203,7 @@
Configuration Header Files
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
Existing Tests
-@@ -311,7 +297,7 @@
- Programming in M4
+@@ -328,7 +314,7 @@
- * M4 Quotation:: Protecting macros from unwanted expansion
--* Invoking autom4te:: The Autoconf executables backbone
-+* autom4te:: The Autoconf executables backbone
- * Programming in M4sugar:: Convenient pure M4 macros
- * Programming in M4sh:: Common shell constructs
+ Using @command{autom4te}
-@@ -388,13 +374,13 @@
+-* autom4te Invocation:: A @acronym{GNU} M4 wrapper
++* autom4te:: A @acronym{GNU} M4 wrapper
+ * Customizing autom4te:: Customizing the Autoconf package
+
+ Programming in M4sugar
+@@ -395,13 +381,13 @@
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
-@@ -418,7 +404,7 @@
+@@ -426,7 +412,7 @@
* Using an Autotest Test Suite:: Autotest and the user
* Writing testsuite.at:: Autotest macros
* Making testsuite Scripts:: Using autom4te to create @command{testsuite}
Using an Autotest Test Suite
-@@ -729,7 +715,7 @@
+@@ -740,7 +726,7 @@
@item
a shell script called @file{config.status} that, when run, will recreate
@item
an optional shell script normally called @file{config.cache}
-@@ -789,10 +775,10 @@
+@@ -800,10 +786,10 @@
@menu
* Writing configure.ac:: What to put in an Autoconf input file
@end menu
@node Writing configure.ac
-@@ -808,7 +794,7 @@
+@@ -819,7 +805,7 @@
or specialized features, @file{configure.ac} might need to contain some
hand-crafted shell commands; see @ref{Portable Shell}. The
@command{autoscan} program can give you a good start in writing
Previous versions of Autoconf promoted the name @file{configure.in},
which is somewhat ambiguous (the tool needed to process this file is not
-@@ -1036,7 +1022,7 @@
+@@ -1047,7 +1033,7 @@
@end display
@section Using @command{autoscan} to Create @file{configure.ac}
@cindex @command{autoscan}
-@@ -1058,7 +1044,7 @@
+@@ -1069,7 +1055,7 @@
use a configuration header file, you must add a call to
@code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might
also have to change or add some @code{#if} directives to your program in
information about a program that can help with that job).
When using @command{autoscan} to maintain a @file{configure.ac}, simply
-@@ -1097,7 +1083,7 @@
+@@ -1108,7 +1094,7 @@
Prepend @var{dir} to the include path. Multiple invocations accumulate.
@end table
@section Using @command{ifnames} to List Conditionals
@cindex @command{ifnames}
-@@ -1106,8 +1092,7 @@
+@@ -1117,8 +1103,7 @@
preprocessor conditionals. If a package has already been set up to have
some portability, @command{ifnames} can thus help you figure out what its
@command{configure} needs to check for. It may help fill in some gaps in a
@command{ifnames} scans all of the C source files named on the command line
(or the standard input, if none are given) and writes to the standard
-@@ -1129,7 +1114,7 @@
+@@ -1140,7 +1125,7 @@
Print the version number of Autoconf and exit.
@end table
@section Using @command{autoconf} to Create @command{configure}
@cindex @command{autoconf}
-@@ -1389,7 +1374,7 @@
+@@ -1234,8 +1219,7 @@
+ @cindex Macro invocation stack
+ Because @command{autoconf} uses @command{autom4te} behind the scenes, it
+ displays a back trace for errors, but not for warnings; if you want
+-them, just pass @option{-W error}. @xref{autom4te Invocation}, for some
+-examples.
++them, just pass @option{-W error}. @xref{autom4te}, for some examples.
+
+ @item --trace=@var{macro}[:@var{format}]
+ @itemx -t @var{macro}[:@var{format}]
+@@ -1247,7 +1231,7 @@
+
+ The @var{format} is a regular string, with newlines if desired, and
+ several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
+-@ref{autom4te Invocation}, for details on the @var{format}.
++@ref{autom4te}, for details on the @var{format}.
+
+ @item --initialization
+ @itemx -i
+@@ -1321,7 +1305,7 @@
@end group
@end example
@section Using @command{autoreconf} to Update @command{configure} Scripts
@cindex @command{autoreconf}
-@@ -1623,8 +1608,8 @@
+@@ -1606,8 +1590,8 @@
source directory; @command{configure} checks for this file's existence to
make sure that the directory that it is told contains the source code in
fact does. Occasionally people accidentally specify the wrong directory
@end defmac
-@@ -1790,7 +1775,7 @@
+@@ -1774,7 +1758,7 @@
when used in @var{output}, or the standard input when used in the
@var{inputs}. You most probably don't need to use this in
@file{configure.ac}, but it is convenient when using the command line
for more details.
The @var{inputs} may be absolute or relative filenames. In the latter
-@@ -2387,7 +2372,7 @@
+@@ -2388,7 +2372,7 @@
@file{config.h} is considered up to date. @xref{Output}, for more
information about @code{AC_OUTPUT}.
configuration-related dependencies.
@node Configuration Headers
-@@ -2448,7 +2433,7 @@
+@@ -2450,7 +2434,7 @@
@menu
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
@end menu
-@@ -2499,10 +2484,10 @@
- @samp{#undef} is strongly discouraged.
+@@ -2504,10 +2488,10 @@
+ comments in preprocessor macros has never been a good idea.
Since it is a tedious task to keep a template header up to date, you may
-use @command{autoheader} to generate it, see @ref{autoheader Invocation}.
@subsection Using @command{autoheader} to Create @file{config.h.in}
@cindex @command{autoheader}
-@@ -6215,7 +6200,7 @@
+@@ -6447,7 +6431,7 @@
files will depend upon @command{bizarre-cc} being the C compiler. If
for some reason the user runs @command{./configure} again, or if it is
run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
inconsistent, composed of results depending upon two different
compilers.
-@@ -6267,7 +6252,7 @@
+@@ -6499,7 +6483,7 @@
@item
@var{variable} is kept during automatic reconfiguration
line argument, including when no cache is used:
@example
-@@ -6608,7 +6593,7 @@
+@@ -7370,11 +7354,11 @@
+ @command{m4} itself.
@menu
- * M4 Quotation:: Protecting macros from unwanted expansion
--* Invoking autom4te:: The Autoconf executables backbone
-+* autom4te:: The Autoconf executables backbone
- * Programming in M4sugar:: Convenient pure M4 macros
- * Programming in M4sh:: Common shell Constructs
+-* autom4te Invocation:: A @acronym{GNU} M4 wrapper
++* autom4te:: A @acronym{GNU} M4 wrapper
+ * Customizing autom4te:: Customizing the Autoconf package
@end menu
-@@ -7111,7 +7096,7 @@
- unexpanded macros. The @command{autoconf} program checks for this problem
- by doing @samp{grep AC_ configure}.
--@node Invoking autom4te
+-@node autom4te Invocation
+@node autom4te
- @section Invoking @command{autom4te}
+ @subsection Invoking @command{autom4te}
- The Autoconf suite, including M4sugar, M4sh, and Autotest, in addition to
-@@ -7394,7 +7379,7 @@
+ The command line arguments are modeled after M4's:
+@@ -7657,7 +7641,7 @@
not.
@end table
@item --preselect=@var{macro}
@itemx -p @var{macro}
-@@ -7845,7 +7830,7 @@
+@@ -7727,8 +7711,8 @@
+ wrapped in between a @samp{begin-language: "@var{language}"},
+ @samp{end-language: "@var{language}"} pair.
+
+-Customizing a language stands for appending options (@pxref{autom4te
+-Invocation}) to the current definition of the language. Options, and
++Customizing a language stands for appending options (@pxref{autom4te})
++to the current definition of the language. Options, and
+ more generally arguments, are introduced by @samp{args:
+ @var{arguments}}. You may use the traditional shell syntax to quote the
+ @var{arguments}.
+@@ -8141,7 +8125,7 @@
When the user runs @samp{autoconf -W error}, warnings from
@code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see
@node Dependencies Between Macros
@section Dependencies Between Macros
-@@ -11642,7 +11627,7 @@
+@@ -12054,7 +12038,7 @@
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
@end menu
@set autoconf
-@@ -11651,7 +11636,7 @@
+@@ -12063,7 +12047,7 @@
@c ============================================== Recreating a Configuration
@chapter Recreating a Configuration
@cindex @command{config.status}
-@@ -11785,7 +11770,7 @@
+@@ -12203,7 +12187,7 @@
@menu
* Obsolete config.status Use:: Different calling convention
* acconfig.h:: Additional entries in @file{config.h.in}
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
-@@ -11795,7 +11780,7 @@
+@@ -12213,7 +12197,7 @@
@section Obsolete @file{config.status} Invocation
@file{config.status} now supports arguments to specify the files to
Before, environment variables had to be used.
@defvar CONFIG_COMMANDS
-@@ -11826,7 +11811,7 @@
+@@ -12244,7 +12228,7 @@
@file{config.status} ignores this variable.
@end defvar
would be:
@example
-@@ -11900,7 +11885,7 @@
+@@ -12318,7 +12302,7 @@
self-contained, and should not depend upon @file{acconfig.h} etc.
@section Using @command{autoupdate} to Modernize @file{configure.ac}
@cindex @command{autoupdate}
-@@ -12750,7 +12735,7 @@
+@@ -13243,7 +13227,7 @@
If you have an @file{aclocal.m4} installed with Autoconf (as opposed to
in a particular package's source directory), you must rename it to
If you distribute @file{install.sh} with your package, rename it to
@file{install-sh} so @code{make} builtin rules won't inadvertently
-@@ -12805,7 +12790,7 @@
+@@ -13298,7 +13282,7 @@
the documentation for them. @xref{Obsolete Macros}, for a table showing the
new names for the old macros. Use the @command{autoupdate} program to
convert your @file{configure.ac} to using the new macro names.
Some macros have been superseded by similar ones that do the job better,
but are not call-compatible. If you get warnings about calling obsolete
-@@ -13302,7 +13287,7 @@
+@@ -13863,7 +13847,7 @@
@menu
* Using an Autotest Test Suite:: Autotest and the user
* Writing testsuite.at:: Autotest macros
* Making testsuite Scripts:: Using autom4te to create @command{testsuite}
@end menu
-@@ -13564,7 +13549,7 @@
+@@ -14125,7 +14109,7 @@
@end defmac
@section Running @command{testsuite} Scripts
@cindex @command{testsuite}
-@@ -13706,7 +13691,7 @@
+@@ -14267,7 +14251,7 @@
An Autotest test suite is to be configured in @var{directory}. This
macro requires the instantiation of @file{@var{directory}/atconfig} from
@file{@var{directory}/atconfig.in}, and sets the default
@end defmac
@item
---- autoconf-2.54/doc/install.texi.wiget Tue Aug 27 10:28:06 2002
-+++ autoconf-2.54/doc/install.texi Fri Oct 18 10:53:29 2002
+@@ -14596,7 +14580,7 @@
+ which can be a very long process for complex @file{configure.ac}.
+
+ This is why all these tools, instead of running directly M4, invoke
+-@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to
++@command{autom4te} (@pxref{autom4te}) which, while answering to
+ a specific demand, stores additional information in
+ @file{autom4te.cache} for future runs. For instance, if you run
+ @command{autoconf}, behind the scenes, @command{autom4te} will also
+diff -Nur autoconf-2.56.orig/doc/install.texi autoconf-2.56/doc/install.texi
+--- autoconf-2.56.orig/doc/install.texi Tue Aug 27 10:28:06 2002
++++ autoconf-2.56/doc/install.texi Mon Nov 18 21:48:00 2002
@@ -225,7 +225,7 @@
overridden in the site shell script).
@section @command{configure} Invocation
@command{configure} recognizes the following options to control how it
---- autoconf-2.54/doc/standards.texi.wiget Wed Apr 10 10:13:19 2002
-+++ autoconf-2.54/doc/standards.texi Fri Oct 18 10:53:29 2002
+diff -Nur autoconf-2.56.orig/doc/standards.texi autoconf-2.56/doc/standards.texi
+--- autoconf-2.56.orig/doc/standards.texi Thu Nov 7 15:22:24 2002
++++ autoconf-2.56/doc/standards.texi Mon Nov 18 21:48:00 2002
@@ -8,9 +8,10 @@
@ifinfo
projects / packages / autoconf.git / commitdiff