From: Tom Tromey Date: Sat, 8 Sep 2018 15:29:18 +0000 (-0600) Subject: Avoid warnings from makeinfo X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=f5a476a7b19f43dce8d15ae3e5deb7027f71ab7b;p=binutils-gdb.git Avoid warnings from makeinfo "make info" gives a number of warnings about the use of a "." in @ref-like commands. These come from the ".info" suffix. I think this suffix is redundant, and removing the suffix also removes the warning. gdb/doc/ChangeLog 2018-09-10 Tom Tromey * gdb.texinfo (Compilation): Use "gcc", not "gcc.info", in @xref. (Machine Code): Use "binutils", not "binutils.info", in @pxref. (Separate Debug Files): Use "ld", not "ld.info", in @ref. * python.texi (Objfiles In Python): Use "ld", not "ld.info", in @ref. --- diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 22987d2defe..dfbb1540ba1 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,10 @@ +2018-09-10 Tom Tromey + + * gdb.texinfo (Compilation): Use "gcc", not "gcc.info", in @xref. + (Machine Code): Use "binutils", not "binutils.info", in @pxref. + (Separate Debug Files): Use "ld", not "ld.info", in @ref. + * python.texi (Objfiles In Python): Use "ld", not "ld.info", in @ref. + 2018-09-10 Tom Tromey PR python/16484: diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f479feffe32..1d96c68d830 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -2019,7 +2019,7 @@ the @sc{gnu} C compiler, provides macro information if you are using the DWARF debugging format, and specify the option @option{-g3}. @xref{Debugging Options,,Options for Debugging Your Program or GCC, -gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}, for more +gcc, Using the @sc{gnu} Compiler Collection (GCC)}, for more information on @value{NGCC} options affecting debug information. You will have the best debugging experience if you use the latest @@ -8938,7 +8938,7 @@ This command controls the passing of target specific information to the disassembler. For a list of valid options, please refer to the @code{-M}/@code{--disassembler-options} section of the @samp{objdump} manual and/or the output of @kbd{objdump --help} -(@pxref{objdump,,objdump,binutils.info,The GNU Binary Utilities}). +(@pxref{objdump,,objdump,binutils,The GNU Binary Utilities}). The default value is the empty string. If it is necessary to specify more than one disassembler option, then @@ -19699,7 +19699,7 @@ also present in the corresponding debug info file. (This is supported only on some operating systems, when using the ELF or PE file formats for binary files and the @sc{gnu} Binutils.) For more details about this feature, see the description of the @option{--build-id} -command-line option in @ref{Options, , Command Line Options, ld.info, +command-line option in @ref{Options, , Command Line Options, ld, The GNU Linker}. The debug info file's name is not specified explicitly by the build ID, but can be computed from the build ID, see below. diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi index e1b79cc30b2..8c4dd8de669 100644 --- a/gdb/doc/python.texi +++ b/gdb/doc/python.texi @@ -4057,7 +4057,7 @@ is the build ID of the objfile. Otherwise, @var{name} is a file name. This is supported only on some operating systems, notably those which use the ELF format for binary files and the @sc{gnu} Binutils. For more details about this feature, see the description of the @option{--build-id} -command-line option in @ref{Options, , Command Line Options, ld.info, +command-line option in @ref{Options, , Command Line Options, ld, The GNU Linker}. @end defun @@ -4093,7 +4093,7 @@ If the objfile does not have a build ID then the value is @code{None}. This is supported only on some operating systems, notably those which use the ELF format for binary files and the @sc{gnu} Binutils. For more details about this feature, see the description of the @option{--build-id} -command-line option in @ref{Options, , Command Line Options, ld.info, +command-line option in @ref{Options, , Command Line Options, ld, The GNU Linker}. @end defvar