public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb@sourceware.org>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>
Subject: Re: [mingw,gdb cvs] make install error on gdb.textinfo
Date: Thu, 09 Feb 2012 13:35:00 -0000	[thread overview]
Message-ID: <4F33CB92.50204@codesourcery.com> (raw)
In-Reply-To: <4F33C57C.6000705@gmail.com>

On 02/09/2012 09:09 PM, asmwarrior wrote:
> Hi, When I run the install command:
> 
> make -C gdb install INSTALL_PROGRAM='install -s'
> DESTDIR=/f/build_gdb/binnew
> 

Hi, thanks for reporting this error.

> ../../../gdb/gdb/doc/gdb.texinfo:24017: `@end' expected `defvar', but
> saw `table
> '.
> ../../../gdb/gdb/doc/gdb.texinfo:23997: No matching `@end defvar'.
> ../../../gdb/gdb/doc/gdb.texinfo:23957: No matching `@end table'.
> makeinfo: Removing output file `gdb.info' due to errors; use --force to

This error exists on linux as well.  Here is the patch to fix.

-- 
Yao (齐尧) 

gdb/doc/

	* gdb.texinfo (Symbols In Python): Add missing `@end defvar'.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 02beed7..4f863dd 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -23997,6 +23997,7 @@ of a symbol.  Each address class is a constant defined in the
 This is @code{True} if evaluating this symbol's value requires a frame
 (@pxref{Frames In Python}) and @code{False} otherwise.  Typically,
 local variables will require a frame, but other symbols will not.
+@end defvar
 
 @defvar Symbol.is_argument
 @code{True} if the symbol is an argument of a function.

      reply	other threads:[~2012-02-09 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 13:04 asmwarrior
2012-02-09 13:35 ` Yao Qi [this message]

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=4F33CB92.50204@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).