This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
*ping* - Re: Fix some texinfo 5.0 warnings in gcc/doc + libiberty
- From: Tobias Burnus <burnus at net-b dot de>
- To: gcc patches <gcc-patches at gcc dot gnu dot org>
- Cc: Gerald Pfeifer <gerald at pfeifer dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 01 Mar 2013 11:08:42 +0100
- Subject: *ping* - Re: Fix some texinfo 5.0 warnings in gcc/doc + libiberty
- References: <512645B2.9040400@net-b.de> <512B2163.8000209@net-b.de>
* PING * â The patch is rather simple and on the verge to be obvious.
http://gcc.gnu.org/ml/gcc-patches/2013-02/msg01106.html
Tobias
Tobias Burnus wrote:
(The attachment contains my original patch (simple rediff) and
Andreas' follow-up patch for libiberty.)
Tobias
Tobias Burnus wrote:
This is a follow up to Jakub's patch.
With texinfo 5.0 one gets a bunch of warnings. This patch reduces the
number of warnings â but there are still warnings to be fixed.
This patch solves most of the issues related to mismatches between
the item order in the @menu and the actual @nodes. As always, there
is the question whether the @node or the item in @menu should be
changed. In one case, I had the choice to either add a new item under
@menu or to change a @section into @subsection. I did the latter.
Tested with "make info" and no new warnings in texinfo 5.0.
Additionally, I used texinfo 4.13a with showed no warnings.
OK for the trunk?
Tobias
PS: I tried the following libiberty patch; it fixes a warning with
texinfo 5.0. But I do not include it as it fails for some reason with
an error with texinfo 4.13:
../../libiberty/libiberty.texi:250: Prev field of node `Functions'
not pointed to.
../../libiberty//obstacks.texi:1: This node (Obstacks) has the bad Next.