diff options
| author | Rical Jasan <ricaljasan@pacific.net> | 2018-01-24 01:03:38 -0800 |
|---|---|---|
| committer | Rical Jasan <ricaljasan@pacific.net> | 2018-02-09 04:40:48 -0800 |
| commit | 1f6676d7da1b7c864e9a5d59fe9162a88bd21952 (patch) | |
| tree | aa1169d408854b670722950671c44aa3c695ed2f /manual/stdio.texi | |
| parent | 15081be9938d0b84634e81b7f0e433ff62406430 (diff) | |
| download | glibc-1f6676d7da1b7c864e9a5d59fe9162a88bd21952.tar.gz | |
manual: Fix Texinfo warnings about improper node names.
A number of cross-references to the GCC info manual cause Texinfo
warnings; e.g.:
./creature.texi:11: warning: @xref node name should not contain `.'
This is due to "gcc.info" being used in the INFO-FILE-NAME (fourth)
argument. Changing it to "gcc" removes these warnings. (Manually
confirmed equivalent behaviour for make info, html, and pdf.)
* manual/creature.texi: Convert references to gcc.info to gcc.
* manual/stdio.texi: Likewise.
* manual/string.texi: Likewise.
Diffstat (limited to 'manual/stdio.texi')
| -rw-r--r-- | manual/stdio.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/manual/stdio.texi b/manual/stdio.texi index 5d7b50c442..38be236991 100644 --- a/manual/stdio.texi +++ b/manual/stdio.texi @@ -1808,7 +1808,7 @@ verifies that the correct number and types of arguments are supplied. There is also a GNU C syntax to tell the compiler that a function you write uses a @code{printf}-style format string. @xref{Function Attributes, , Declaring Attributes of Functions, -gcc.info, Using GNU CC}, for more information. +gcc, Using GNU CC}, for more information. @node Table of Output Conversions @subsection Table of Output Conversions @@ -2730,7 +2730,7 @@ This tells the compiler that @code{eprintf} uses a format string like the format string appears as the first argument; and the arguments to satisfy the format begin with the second. @xref{Function Attributes, , Declaring Attributes of Functions, -gcc.info, Using GNU CC}, for more information. +gcc, Using GNU CC}, for more information. @node Parsing a Template String @subsection Parsing a Template String @@ -3478,7 +3478,7 @@ verifies that the correct number and types of arguments are supplied. There is also a GNU C syntax to tell the compiler that a function you write uses a @code{scanf}-style format string. @xref{Function Attributes, , Declaring Attributes of Functions, -gcc.info, Using GNU CC}, for more information. +gcc, Using GNU CC}, for more information. @node Table of Input Conversions @subsection Table of Input Conversions @@ -4033,7 +4033,7 @@ know that a function uses a @code{scanf}-style format string. Then it can check the number and types of arguments in each call to the function, and warn you when they do not match the format string. For details, see @ref{Function Attributes, , Declaring Attributes of Functions, -gcc.info, Using GNU CC}. +gcc, Using GNU CC}. @node EOF and Errors @section End-Of-File and Errors |