- updated to 1.12

[packages/automake.git] / automake-info.patch

--- automake-1.12/doc/automake.texi.orig	2012-04-21 16:38:05.000000000 +0200
+++ automake-1.12/doc/automake.texi	2012-05-09 15:48:51.421519783 +0200
@@ -36,15 +36,11 @@
 @end quotation
 @end copying
 
-@dircategory Software development
+@dircategory Programming tools:
 @direntry
-* Automake: (automake).         Making GNU standards-compliant Makefiles.
-@end direntry
-
-@dircategory Individual utilities
-@direntry
-* aclocal-invocation: (automake)aclocal Invocation.   Generating aclocal.m4.
-* automake-invocation: (automake)automake Invocation. Generating Makefile.in.
+* Automake: (automake).			Making GNU standards-compliant Makefiles
+* aclocal-invocation: (automake)aclocal.	Generating aclocal.m4
+* automake-invocation: (automake)automake.	Generating Makefile.in
 @end direntry
 
 @titlepage
@@ -97,7 +93,7 @@
 * Autotools Introduction::      An Introduction to the Autotools
 * Generalities::                General ideas
 * Examples::                    Some example packages
-* automake Invocation::         Creating a Makefile.in
+* automake::                    Creating a Makefile.in
 * configure::                   Scanning configure.ac, using aclocal
 * Directories::                 Declaring subdirectories
 * Programs::                    Building programs and libraries
@@ -175,7 +171,7 @@
 
 * Requirements::                Configuration requirements
 * Optional::                    Other things Automake recognizes
-* aclocal Invocation::          Auto-generating aclocal.m4
+* aclocal::                     Auto-generating aclocal.m4
 * Macros::                      Autoconf macros supplied with Automake
 
 Auto-generating aclocal.m4
@@ -1682,7 +1678,7 @@
 When starting a new project, we suggest you start with such a simple
 @file{configure.ac}, and gradually add the other tests it requires.
 The command @command{autoscan} can also suggest a few of the tests
-your package may need (@pxref{autoscan Invocation, , Using
+your package may need (@pxref{autoscan, , Using
 @command{autoscan} to Create @file{configure.ac}, autoconf, The
 Autoconf Manual}).
 
@@ -2501,7 +2497,7 @@
 would be chosen by automake; they would be @file{false-true.o} and
 @file{true-true.o}. (The name of the object files rarely matters.)
 
-@node automake Invocation
+@node automake
 @chapter Creating a @file{Makefile.in}
 @c This node used to be named "Invoking automake".  This @anchor
 @c allows old links to still work.
@@ -2759,7 +2755,7 @@
 @menu
 * Requirements::                Configuration requirements
 * Optional::                    Other things Automake recognizes
-* aclocal Invocation::          Auto-generating aclocal.m4
+* aclocal::                     Auto-generating aclocal.m4
 * Macros::                      Autoconf macros supplied with Automake
 @end menu
 
@@ -3136,11 +3132,11 @@
 @code{m4_include} is seldom used by @file{configure.ac} authors, but
 can appear in @file{aclocal.m4} when @command{aclocal} detects that
 some required macros come from files local to your package (as opposed to
-macros installed in a system-wide directory, @pxref{aclocal Invocation}).
+macros installed in a system-wide directory, @pxref{aclocal}).
 
 @end ftable
 
-@node aclocal Invocation
+@node aclocal
 @section Auto-generating aclocal.m4
 @c This node used to be named "Invoking automake".  This @anchor
 @c allows old links to still work.
@@ -3325,7 +3321,7 @@
 
 @vindex WARNINGS
 The environment variable @env{WARNINGS} is honored in the same
-way as it is for @command{automake} (@pxref{automake Invocation}).
+way as it is for @command{automake} (@pxref{automake}).
 
 @end table
 
@@ -3633,12 +3629,12 @@
 
 @code{ACLOCAL_AMFLAGS} contains options to pass to @command{aclocal}
 when @file{aclocal.m4} is to be rebuilt by @command{make}.  This line is
-also used by @command{autoreconf} (@pxref{autoreconf Invocation, ,
+also used by @command{autoreconf} (@pxref{autoreconf, ,
 Using @command{autoreconf} to Update @file{configure} Scripts,
 autoconf, The Autoconf Manual}) to run @command{aclocal} with suitable
-options, or by @command{autopoint} (@pxref{autopoint Invocation, ,
+options, or by @command{autopoint} (@pxref{autopoint, ,
 Invoking the @command{autopoint} Program, gettext, GNU gettext tools})
-and @command{gettextize} (@pxref{gettextize Invocation, , Invoking the
+and @command{gettextize} (@pxref{gettextize, , Invoking the
 @command{gettextize} Program, gettext, GNU gettext tools}) to locate
 the place where Gettext's macros should be installed.  So even if you
 do not really care about the rebuild rules, you should define
@@ -4081,8 +4077,8 @@
 releases, you should not use any of them in new code.  @emph{All
 these macros will be removed in the next major Automake version};
 if you are still using them, running @command{autoupdate} should
-adjust your @file{configure.ac} automatically (@pxref{autoupdate
-Invocation, , Using @command{autoupdate} to Modernize
+adjust your @file{configure.ac} automatically (@pxref{autoupdate,
+, Using @command{autoupdate} to Modernize
 @file{configure.ac}, autoconf, The Autoconf Manual}).
 @emph{Do it NOW!}
 
@@ -5462,7 +5458,7 @@
 passed to the tool invoked by @command{libtool} (hence the use of
 @samp{@var{library}_LDFLAGS} for libtool linking flags).  Generic
 options include @option{--tag=@var{tag}} and @option{--silent}
-(@pxref{Invoking libtool, , Invoking @command{libtool}, libtool, The
+(@pxref{libtool, , Invoking @command{libtool}, libtool, The
 Libtool Manual} for more options) should appear before the mode
 selection on the command line; in @file{Makefile.am}s they should
 be listed in the @samp{@var{library}_LIBTOOLFLAGS} variable.
@@ -5536,7 +5532,7 @@
 Since Automake 1.6, it has been decided that running
 @command{libtoolize} was none of Automake's business.  Instead, that
 functionality has been moved into the @command{autoreconf} command
-(@pxref{autoreconf Invocation, , Using @command{autoreconf}, autoconf,
+(@pxref{autoreconf, , Using @command{autoreconf}, autoconf,
 The Autoconf Manual}).  If you do not want to remember what to run and
 when, just learn the @command{autoreconf} command.  Hopefully,
 replacing existing @file{bootstrap.sh} or @file{autogen.sh} scripts by
@@ -10296,7 +10292,7 @@
 @cindex Option, @option{-W@var{category}}
 @cindex Option, @option{--warnings=@var{category}}
 These options behave exactly like their command-line counterpart
-(@pxref{automake Invocation}).  This allows you to enable or disable some
+(@pxref{automake}).  This allows you to enable or disable some
 warning categories on a per-file basis.  You can also setup some warnings
 for your entire project; for instance, try @samp{AM_INIT_AUTOMAKE([-Wall])}
 in your @file{configure.ac}.
@@ -10906,7 +10902,7 @@
 that is not required by POSIX 2008 but is widely supported in
 practice.  The @option{silent-rules} option thus turns off warnings
 about recursive variable expansion, which are in turn enabled by
-@option{-Wportability} (@pxref{automake Invocation}).  On the rare
+@option{-Wportability} (@pxref{automake}).  On the rare
 @command{make} implementations that do not support nested variable
 expansion, whether rules are silent is always determined at configure
 time, and cannot be overridden at make time.  Future versions of POSIX
@@ -11133,7 +11129,7 @@
 settings of Automake, or replace some of its rules.  Overriding
 Automake rules is often inadvisable, particularly in the topmost
 directory of a package with subdirectories.  The @option{-Woverride}
-option (@pxref{automake Invocation}) comes in handy to catch overridden
+option (@pxref{automake}) comes in handy to catch overridden
 definitions.
 
 Note that Automake does not make any distinction between rules with
@@ -11581,7 +11577,7 @@
 @end example
 
 The use of @option{--force-missing} ensures that auxiliary tools will be
-overridden by new versions (@pxref{automake Invocation}).
+overridden by new versions (@pxref{automake}).
 
 It is important to regenerate all these files each time Automake is
 upgraded, even between bug fixes releases.  For instance, it is not