This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: make info probs on trunk?
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: make info probs on trunk?
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Mon, 17 Apr 2000 05:00:07 -0400 (EDT)
- CC: GDB Patches <gdb-patches at sourceware dot cygnus dot com>
- References: <38FACB19.C214A165@cygnus.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
On Mon, 17 Apr 2000, Andrew Cagney wrote:
> Running makeinfo 4.0 I'm seeing:
>
> /home/scratch/texinfo-4.0/makeinfo/makeinfo -I
> /home/scratch/GDB/src/gdb/doc/../../readline/doc -I
> /home/scratch/GDB/src/gdb/doc -o ./gdb.info gdb.texinfo
> gdb.texinfo:9451: warning: unlikely character , in @var.
I will correct this ASAP.
> /home/scratch/GDB/src/gdb/doc/../../readline/doc/rluser.texinfo:42:
> warning: @sc argument all uppercase, thus no effect.
> /home/scratch/GDB/src/gdb/doc/../../readline/doc/rluser.texinfo:1269:
> warning: @sc argument all uppercase, thus no effect.
These are not new: rluser.texinfo needs to be changed to prevent these
warnings. The problem is, the changes need to be reported back to the
Readline maintainers. Since these are just warnings, I never got to
that... Should I?
> /home/scratch/texinfo-4.0/makeinfo/makeinfo -o gdbint.info
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo:1038: warning: @sc argument
> all uppercase, thus no effect.
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo:2630: Next reference to
> nonexistent node `Porting GDB'.
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo:2912: `Porting
> @value{GDBN}' has no Up field.
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo:2995: Prev reference to
> nonexistent node `Porting GDB'.
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo:88: Menu reference to
> nonexistent node `Porting GDB'.
> /home/scratch/GDB/src/gdb/doc/gdbint.texinfo:2912: warning: unreferenced
> node `Porting @value{GDBN}'.
This last warning *is* the reason for these problems: you cannot use
@value (or any other @ command) in a node name, unless you do it
consistently in all places that node is referenced. This is explained
in the Texinfo manual.
I will remove @value from the node at line 2912 (using @ commands in node
names should be generally discouraged).