libtool-info.patch

--- libtool-2.6.2/doc/libtool.texi.orig	2026-07-16 15:56:58.000000000 +0200
+++ libtool-2.6.2/doc/libtool.texi	2026-08-26 05:33:52.219501033 +0200
@@ -31,16 +31,12 @@ and with no Back-Cover Texts.  A copy of
 the section entitled ``GNU Free Documentation License''.
 @end copying
 
-@dircategory Software development
+@dircategory Programming tools:
 @direntry
-* Libtool: (libtool).           Generic shared library support script.
-@end direntry
-
-@dircategory Individual utilities
-@direntry
-* libtool-invocation: (libtool)Invoking libtool. Running the @code{libtool} script.
-* libtoolize: (libtool)Invoking libtoolize.      Adding libtool support.
-* libtool-next-version: (libtool)Invoking libtool-next-version. Running the @code{libtool-next-version} wizard.
+* Libtool: (libtool).			Generic shared library support script
+* libtool-invocation: (libtool)libtool.	Running the @code{libtool} script
+* libtoolize: (libtool)libtoolize.	Adding libtool support
+* libtool-next-version: (libtool)libtool-next-version.	Running the @code{libtool-next-version} wizard
 @end direntry
 
 @titlepage
@@ -74,7 +70,7 @@ GNU Libtool.
 * Introduction::                What the heck is libtool?
 * Libtool paradigm::            How libtool's view of libraries is different.
 * Using libtool::               Example of using libtool to build libraries.
-* Invoking libtool::            Running the @code{libtool} script.
+* libtool::                     Running the @code{libtool} script.
 * Integrating libtool::         Using libtool in your own packages.
 * Other languages::             Using libtool without a C compiler.
 * Versioning::                  Using library interface versions.
@@ -139,7 +135,7 @@ Configuring libtool
 
 Including libtool in your package
 
-* Invoking libtoolize::         @code{libtoolize} command line options.
+* libtoolize::                  @code{libtoolize} command line options.
 * Autoconf and LTLIBOBJS::      Autoconf automates LTLIBOBJS generation.
 
 Using libtool with other languages
@@ -1174,7 +1170,7 @@ Another common situation where static li
 creating a standalone binary.  Use libtool to do the linking and add the
 @option{-all-static} flag.
 
-@node Invoking libtool
+@node libtool
 @chapter Invoking @command{libtool}
 @pindex libtool
 @cindex libtool command options
@@ -2619,8 +2615,8 @@ the file itself.
 @end defmac
 
 @pindex aclocal
-When you invoke the @command{libtoolize} program (@pxref{Invoking
-libtoolize}), it will tell you where to find a definition of
+When you invoke the @command{libtoolize} program (@pxref{libtoolize}),
+it will tell you where to find a definition of
 @code{LT_INIT}.  If you use Automake, the @command{aclocal} program
 will automatically add @code{LT_INIT} support to your
 @file{configure} script when it sees the invocation of @code{LT_INIT}
@@ -2677,11 +2673,11 @@ You should use the @command{libtoolize}
 copying these files into your package.
 
 @menu
-* Invoking libtoolize::         @code{libtoolize} command line options.
+* libtoolize::                  @code{libtoolize} command line options.
 * Autoconf and LTLIBOBJS::      Autoconf automates LTLIBOBJS generation.
 @end menu
 
-@node Invoking libtoolize
+@node libtoolize
 @subsection Invoking @command{libtoolize}
 @pindex libtoolize
 @cindex libtoolize command options
@@ -3033,7 +3029,7 @@ the compiler command being used to compi
 a tag, then it exits immediately with a fatal error.
 
 The tag can also be specified using @command{libtool}'s
-@option{--tag=@var{tag}} option (@pxref{Invoking libtool}).  It is a good
+@option{--tag=@var{tag}} option (@pxref{libtool}).  It is a good
 idea to do so in @file{Makefile} rules, because that will allow users to
 substitute the compiler without relying on @command{libtool} inference
 heuristics.  When no tag is specified, @command{libtool} will default
@@ -3200,7 +3196,7 @@ with any other release.
 @menu
 * Manual version info update::    Updating version info manually.
 * Guided version info update::    Using the libtool-next-version program.
-* Invoking libtool-next-version:: @code{libtool-next-version} command line options.
+* libtool-next-version::          @code{libtool-next-version} command line options.
 @end menu
 
 @node Manual version info update
@@ -3299,7 +3295,7 @@ Then you are ready to invoke the wizard
 $ libtool-next-version /tmp/prev/lib/libfoo.so /tmp/curr/lib/libfoo.so
 @end example
 
-@node Invoking libtool-next-version
+@node libtool-next-version
 @subsection Invoking @command{libtool-next-version}
 @pindex libtool-next-version
 @cindex libtool-next-version command options
@@ -4989,7 +4985,7 @@ into any program is left as an exercise
 @defmac LT_CONFIG_LTDL_DIR (@var{directory})
 Declare @var{directory} to be the location of the @code{libltdl}
 source files, for @command{libtoolize --ltdl} to place
-them. @xref{Invoking libtoolize}, for more details.  Provided that you
+them. @xref{libtoolize}, for more details.  Provided that you
 add an appropriate @code{LT_CONFIG_LTDL_DIR} call in your
 @file{configure.ac} before calling @command{libtoolize}, the
 appropriate @code{libltdl} files will be installed automatically.