Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)
Date: Mon, 10 Oct 2011 13:54:00 -0000	[thread overview]
Message-ID: <E1RDGIs-0005T4-Eo@fencepost.gnu.org> (raw)
In-Reply-To: <201110101340.p9ADeDSd024038@d06av02.portsmouth.uk.ibm.com>	(uweigand@de.ibm.com)

> Date: Mon, 10 Oct 2011 15:40:13 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org
> 
> Jan Kratochvil wrote:
> 
> > --- a/gdb/doc/gdb.texinfo
> > +++ b/gdb/doc/gdb.texinfo
> 
> > +Frames #0 and #2 are real, #1 is a virtual tail call frame.  The code can have
> > +possible execution paths
> > +@code{main@arrow{}a@arrow{}b@arrow{}c@arrow{}d@arrow{}f} or
> > +@code{main@arrow{}a@arrow{}b@arrow{}e@arrow{}f}, @value{GDBN} cannot find which
> > +one from the inferior state.
> 
> This causes make install to fail for me with:
> 
> makeinfo --split-size=5000000 --split-size=5000000 -I /home/kwerner/dailybuild/spu-tc-2011-10-10/gdb-head/src/gdb/doc/../../readline/doc -I /home/kwerner/dailybuild/spu-tc-2011-10-10/gdb-head/src/gdb/doc/../mi -I /home/kwerner/dailybuild/spu-tc-2011-10-10/gdb-head/src/gdb/doc \
>                 -o gdb.info /home/kwerner/dailybuild/spu-tc-2011-10-10/gdb-head/src/gdb/doc/gdb.texinfo
> /home/kwerner/dailybuild/spu-tc-2011-10-10/gdb-head/src/gdb/doc/gdb.texinfo:9794: Unknown command `arrow'.

@arrow is from a relatively new version of Texinfo.  What version do
you have on that machine?


  reply	other threads:[~2011-10-10 13:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 19:50 [patch 04/12] entryval#3: Virtual tail call frames Jan Kratochvil
2011-10-09 19:27 ` [commit] " Jan Kratochvil
2011-10-09 20:23   ` Jan Kratochvil
2011-10-10 13:40 ` doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames) Ulrich Weigand
2011-10-10 13:54   ` Eli Zaretskii [this message]
2011-10-10 13:58     ` Ulrich Weigand
2011-10-10 14:58       ` [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)] Jan Kratochvil
2011-10-10 15:16         ` Pedro Alves
2011-10-10 15:31           ` Jan Kratochvil
2011-10-10 15:51             ` Pedro Alves
2011-10-10 18:47               ` Jan Kratochvil
2011-10-10 19:11                 ` Eli Zaretskii
2011-10-10 21:56                 ` Pedro Alves
2011-10-10 22:19                   ` Andreas Schwab
2011-10-11 23:34                   ` Jan Kratochvil
2011-10-12 15:26                     ` Pedro Alves
2011-10-12 15:56                       ` Jan Kratochvil
2011-10-25 14:35                     ` Joel Brobecker
2011-10-25 14:47                       ` Jan Kratochvil
2011-10-25 16:09                         ` Joel Brobecker
2011-10-10 16:10             ` Eli Zaretskii
2011-10-10 16:15               ` Jan Kratochvil
2011-10-10 16:09           ` Eli Zaretskii

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=E1RDGIs-0005T4-Eo@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=uweigand@de.ibm.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