branch: master
commit e22141c0c5e289fdff11cdbf76a9799a06ab43c6
Author: Ileana Dumitrescu <ileanadumitresc...@gmail.com>
AuthorDate: Tue Jun 18 19:46:26 2024 +0300

    libtool: Update pxref to remove texinfo warning
    
    Building the documentation contains this warning:
      libtool.texi:1333: warning: @pxref node name should not contain `.'
    
    Now, users will be linked to the top of the autoconf manual and need
    to manually scroll to the section specified.
    
    * doc/libtool.texi: Specify section header instead of duplicating
      autoconf manual name.
---
 doc/libtool.texi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/libtool.texi b/doc/libtool.texi
index 9da9f706..b212b24c 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -1330,10 +1330,10 @@ category is @command{all}. To disable warnings, use the 
category
 
 The current @command{libtool} implementation is done with a shell script
 that needs to be invoked by the shell that @command{configure} chose for
-configuring @command{libtool} (@pxref{config.status Invocation, , The
-Autoconf Manual, autoconf, The Autoconf Manual}).  This shell is set in
-the she-bang (@samp{#!}) line of the @command{libtool} script.  Using a
-different shell may cause undefined behavior.
+configuring @command{libtool} (@pxref{, , config.status Invocation,
+autoconf, The Autoconf Manual}).  This shell is set in the she-bang
+(@samp{#!}) line of the @command{libtool} script.  Using a different
+shell may cause undefined behavior.
 
 The @var{mode-args} are a variable number of arguments, depending on the
 selected operation mode.  In general, each @var{mode-arg} is interpreted

Reply via email to