From: Andrew Cagney <cagney@gnu.org>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Texinfo build errors
Date: Wed, 09 Feb 2005 19:21:00 -0000 [thread overview]
Message-ID: <420A5B67.8010605@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0502090853350.31714@knuth.amplepower.com>
Theodore A. Roth wrote:
> Hi,
>
> I just tried to build the latest from cvs and got these fatal errors
> during the 'make install' stage:
>
> makeinfo --split-size=5000000 -I ../../../src/gdb/doc/../../readline/doc
> -I ../../../src/gdb/doc/../mi -I ../../../src/gdb/doc \
> -o gdb.info ../../../src/gdb/doc/gdb.texinfo
> ../../../src/gdb/doc/gdb.texinfo:7035: warning: @strong{Note:} produces
> a spurious cross-reference in Info; reword to avoid that.
> ../../../src/gdb/doc/gdb.texinfo:21102: @dots expected braces.
> ../../../src/gdb/doc/gdb.texinfo:21102: @- missing close brace.
> makeinfo: Removing output file `gdb.info' due to errors; use --force to
> preserve.
>
>
> The attached patch get things working again for my system (debian-sarge,
> texinfo-4.7, teTeX-2.0.2). I'm no texinfo wizard, so please let me know
> if there are better fixes.
>
> This is probably an obvious fix, but I'm asking for approval anyways.
It's definitly better than not building (checking the nightly snaps it
seems they also barf with the same error). I'd commit it is obvious for
that reason.
Andrew
> ---
> Ted Roth
> PGP Key ID: 0x18F846E9
>
>
> ------------------------------------------------------------------------
>
> 2005-02-09 Theodore A. Roth <troth@openavr.org>
>
> * gdb.texinfo (General Query Packets): Fix texinfo compile warning and
> error.
>
> Index: gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.231
> diff -u -p -p -r1.231 gdb.texinfo
> --- gdb.texinfo 3 Feb 2005 16:11:38 -0000 1.231
> +++ gdb.texinfo 9 Feb 2005 17:03:33 -0000
> @@ -7032,7 +7032,7 @@ experiment.
> This command takes no arguments. It ends the trace experiment, and
> stops collecting data.
>
> -@strong{Note:} a trace experiment and data collection may stop
> +@strong{Note}: a trace experiment and data collection may stop
> automatically if any tracepoint's passcount is reached
> (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full.
>
> @@ -21098,7 +21098,7 @@ differently, so the precise meaning of t
>
> Reply:
> @table @asis
> -@item @var{XX@dots}
> +@item @var{XX@dots{}}
> Hex encoded (big endian) bytes representing the address of the thread
> local storage requested.
>
next prev parent reply other threads:[~2005-02-09 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 18:49 Theodore A. Roth
2005-02-09 19:21 ` Andrew Cagney [this message]
2005-02-09 19:40 ` Theodore A. Roth
2005-02-09 20:27 ` Eli Zaretskii
2005-02-09 20:00 ` 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=420A5B67.8010605@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=troth@openavr.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