mirror of
https://sourceware.org/git/glibc.git
synced 2024-11-23 17:53:37 +08:00
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.
This commit is contained in:
parent
15081be993
commit
1f6676d7da
@ -1,3 +1,9 @@
|
||||
2018-02-09 Rical Jasan <ricaljasan@pacific.net>
|
||||
|
||||
* manual/creature.texi: Convert references to gcc.info to gcc.
|
||||
* manual/stdio.texi: Likewise.
|
||||
* manual/string.texi: Likewise.
|
||||
|
||||
2018-02-07 Joseph Myers <joseph@codesourcery.com>
|
||||
|
||||
[BZ #17979]
|
||||
|
@ -8,7 +8,7 @@ is controlled by which @dfn{feature test macros} you define.
|
||||
If you compile your programs using @samp{gcc -ansi}, you get only the
|
||||
@w{ISO C} library features, unless you explicitly request additional
|
||||
features by defining one or more of the feature macros.
|
||||
@xref{Invoking GCC,, GNU CC Command Options, gcc.info, The GNU CC Manual},
|
||||
@xref{Invoking GCC,, GNU CC Command Options, gcc, The GNU CC Manual},
|
||||
for more information about GCC options.@refill
|
||||
|
||||
You should define these macros by using @samp{#define} preprocessor
|
||||
|
@ -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
|
||||
|
@ -1087,7 +1087,7 @@ are often easier and safer automatic techniques that cause buffer
|
||||
overruns to reliably terminate a program, such as GCC's
|
||||
@option{-fcheck-pointer-bounds} and @option{-fsanitize=address}
|
||||
options. @xref{Debugging Options,, Options for Debugging Your Program
|
||||
or GCC, gcc.info, Using GCC}. Because truncation functions can mask
|
||||
or GCC, gcc, Using GCC}. Because truncation functions can mask
|
||||
application bugs that would otherwise be caught by the automatic
|
||||
techniques, these functions should be used only when the application's
|
||||
underlying logic requires truncation.
|
||||
|
Loading…
Reference in New Issue
Block a user