Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix in features/Makefile
Date: Sun, 24 Aug 2008 22:38:00 -0000	[thread overview]
Message-ID: <20080824223751.GB7324@caradoc.them.org> (raw)
In-Reply-To: <m3prnycmh4.fsf@fleche.redhat.com>

On Sun, Aug 24, 2008 at 12:11:03PM -0600, Tom Tromey wrote:
> When regenerating some files in features using features/Makefile, I
> saw some strange control characters show up at the start of the
> generated files.
> 
> This patch changes features/Makefile to use gdb's logging feature
> rather than redirection to create the output files.  This fixed the
> problem I saw.

But why did it?  If you can't redirect GDB's output, something's
wrong.

> This patch also makes it so that the .c files are always rebuilt in
> response to a 'make'.  Without the FORCE code, make was not running
> the rule for me.

If you're going to change the generating code, IMO it's reasonable to
remove and remake the generated files by hand...

> Also, it would be nice if someone documented which .xml->.c
> translations are to be checked in.  I ran the rule with XMLTOC set to
> all the .xml files under features, and I got a bunch of new files that
> aren't in the repository.  IMO the canonical list ought to be set in
> features/Makefile somewhere.

Sounds reasonable.  It's all the ones with a full target description
(rather than a single feature), I believe.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-24 22:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 18:12 Tom Tromey
2008-08-24 22:38 ` Daniel Jacobowitz [this message]
2008-08-25  0:03   ` Tom Tromey
2008-08-25  2:36     ` Daniel Jacobowitz
2008-08-25  4:04       ` Tom Tromey
2008-08-25 12:12         ` Daniel Jacobowitz
2008-10-06 20:39           ` Tom Tromey

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=20080824223751.GB7324@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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