Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: sellcey@imgtec.com
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [doc RFA] stabs.texinfo: @include gdb-cfg.texi.
Date: Fri, 17 Jul 2015 22:38:00 -0000	[thread overview]
Message-ID: <CADPb22TMoc3VhaMHeqgwYD4YkK3_tSzBe1aXpaN26Yn_5v2Y-A@mail.gmail.com> (raw)
In-Reply-To: <1437172207.19674.100.camel@ubuntu-sellcey>

On Fri, Jul 17, 2015 at 3:30 PM, Steve Ellcey <sellcey@imgtec.com> wrote:
> On Thu, 2015-07-16 at 16:30 +0000, Doug Evans wrote:
>
>> 2015-07-16  Doug Evans  <dje@google.com>
>>
>>       * stabs.texinfo: @include gdb-cfg.texi.
>>
>> diff --git a/gdb/doc/stabs.texinfo b/gdb/doc/stabs.texinfo
>> index 15c4152..c4ea037 100644
>> --- a/gdb/doc/stabs.texinfo
>> +++ b/gdb/doc/stabs.texinfo
>> @@ -3,6 +3,10 @@
>>   @setchapternewpage odd
>>   @settitle STABS
>>
>> +@c man begin INCLUDE
>> +@include gdb-cfg.texi
>> +@c man end
>> +
>>   @c @finalout
>>
>>   @c This is a dir.info fragment to support semi-automated addition of
>
> This patch breaks my parallel gdb builds (though the bug may be a latent
> one that this change finally causes to trigger).  On my machine my
> parallel GDB build dies with:
>
> ./gdb-cfg.texi:16: @include `GDBvn.texi': No such file or directory.
>
> And then later in the log I see:
>
> mv GDBvn.new GDBvn.texi
>
> I think there is a missing dependency in the doc/Makefile.in to say that
> GDBvn.texi needs to be built before gdb-cfg.texi.

Bleah.
I think we just need to update STABS_DOC_BUILD_INCLUDES
to be like GDB_DOC_BUILD_INCLUDES.
I'll take care of it.

Thanks for the report.


  reply	other threads:[~2015-07-17 22:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 16:31 Doug Evans
2015-07-16 16:34 ` Eli Zaretskii
2015-07-17 22:30 ` Steve Ellcey
2015-07-17 22:38   ` Doug Evans [this message]
2015-07-17 22:59 Doug Evans
2015-07-20 17:07 ` Steve Ellcey
2015-07-20 17:09   ` Doug Evans
2015-07-20 17:17     ` Steve Ellcey

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=CADPb22TMoc3VhaMHeqgwYD4YkK3_tSzBe1aXpaN26Yn_5v2Y-A@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sellcey@imgtec.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