From: Elena Zannoni <ezannoni@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: eliz@is.elta.co.il
Subject: make info warnings
Date: Wed, 15 Jan 2003 14:47:00 -0000 [thread overview]
Message-ID: <15909.30080.816161.5429@localhost.redhat.com> (raw)
Am I the only one getting these warnings when building the docs?
makeinfo -I /home/ezannoni/sources/src/gdb/doc/../../readline/doc -I /home/ezannoni/sources/src/gdb/doc/../mi -I /home/ezannoni/sources/src/gdb/doc \
-o gdb.info /home/ezannoni/sources/src/gdb/doc/gdb.texinfo
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11908: warning: unlikely character [ in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11908: warning: unlikely character ] in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11919: warning: unlikely character [ in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11919: warning: unlikely character ] in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11926: warning: unlikely character [ in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11926: warning: unlikely character [ in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11926: warning: unlikely character ] in @var.
/home/ezannoni/sources/src/gdb/doc/gdb.texinfo:11926: warning: unlikely character ] in @var.
these are the lines that generate the warnings.
@item htrace record @var{[data]*}
@item htrace rewind @var{[filename]}
@item htrace print @var{[start [len]]}
It it easy to eliminate the warnings by using for instance @emph{} instead of
@var{}, but the look of the text changes slightly.
Eli, is there a correct way to fix this?
thanks
Elena
next reply other threads:[~2003-01-15 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 14:47 Elena Zannoni [this message]
2003-01-15 15:59 ` Andreas Schwab
2003-01-15 17:28 ` Eli Zaretskii
2003-01-15 17:57 ` Elena Zannoni
2003-01-15 17:52 ` Elena Zannoni
2003-01-15 16:39 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15909.30080.816161.5429@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox