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  <tom@tromey.com>

	* 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.
This commit is contained in:
Tom Tromey
2018-09-08 09:29:18 -06:00
parent a154931ef1
commit f5a476a7b1
3 changed files with 12 additions and 5 deletions

View File

@ -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