Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco, 6.0] (C) and other fixes
Date: Fri, 08 Aug 2003 13:55:00 -0000	[thread overview]
Message-ID: <3F33ABDB.9060102@redhat.com> (raw)
In-Reply-To: <9743-Fri08Aug2003102929+0300-eliz@elta.co.il>

>> Date: Thu, 07 Aug 2003 17:35:58 -0400
>> From: Andrew Cagney <ac131313@redhat.com>
> 
>> >> 
>> >> I think, though, that there is a makeinfo bug here.  It should have 
>> >> reported an error due to references to missing sections.
> 
>> > 
>> > 
>> > What references were pointing to the missing sections?
> 
>> 
>> If I add @bye to the end of agentexpr.texi "make info" runs cleanly and 
>> the document looks ok (the @bye appears to be ignored).  However, if the 
>> @bye is put in gdb.texinfo just after the @include agentexpr.texi, or if 
>> @bye is put at the start of agentexpr.texi, "make info" gets errors 
>> about undefined references to "Copying", "Index" and "GNU Free ...".
>> 
>> TeX, on the other hand `dies a death' in both cases (which is what I'd 
>> expect makeinfo to do).
> 
> 
> I'm confused: where is the bug in makeinfo that you thought about?
> AFAIU, makeinfo behaves correctly: produces a valid Info document in
> the first case and complains about the second.

It should complain in all cases.  For some strange reason makeinfo 
silently ignores @bye as the last line of an included file (well at 
least the file agentexpr.texi). texinfo doesn't do this.  @include mentions:

> Likewise, you should not end an included file with an
> `@bye' command; nothing after `@bye' is formatted.

enjoy,
Andrew



  reply	other threads:[~2003-08-08 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 16:11 Andrew Cagney
2003-08-04 16:21 ` Daniel Jacobowitz
2003-08-07  4:24   ` Andrew Cagney
2003-08-07  5:08     ` Eli Zaretskii
2003-08-07 21:36       ` Andrew Cagney
2003-08-08  7:33         ` Eli Zaretskii
2003-08-08 13:55           ` Andrew Cagney [this message]
2003-08-04 20:29 ` Eli Zaretskii
2003-08-04 20:43   ` Andrew Cagney

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=3F33ABDB.9060102@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=eliz@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