Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Enable PO files.
Date: Fri, 30 Jul 2004 18:56:00 -0000	[thread overview]
Message-ID: <87isc575ry.fsf@fleche.redhat.com> (raw)
In-Reply-To: <41091DEB.9020904@gnu.org>

>>>>> "Andrew" == Andrew Cagney <cagney@gnu.org> writes:

Andrew> - the output is put in the _build_ directory (instead of RO srcdir)

The only issue with this, I think, is how releases are made -- but I
see from the patch that you already dealt with this.

Andrew> - insisted on using ../intl/
Andrew> I didn't borrow that - GDB will still use an installed intl/ (I'm
Andrew> wondering if its time to boot intl/ out of GDB's distro).

Hmm, I thought the point of doing this is that the stuff in intl,
while readily available on Linux boxes, isn't so available elsewhere.
I could be behind the times, though, I haven't looked at the nuts and
bolts of gettext building in years.

Andrew> +      find * \
Andrew> +	  -name '*-stub.c' -prune -o \
Andrew> +	  -name 'testsuite' -prune -o \
Andrew> +	  -name 'init.c' -prune -o \
Andrew> +	  -name '*.[hc]' -print

I never liked using find for things like this, since I tend to push
files out of the way by "mv foo.c hacked-foo.c", but I can understand
why you'd do it this way.  I suppose it could only negatively affect
some subset of "real gdb developers" anyway, provided releases are
always done from a pristine checkout.

Tom


  parent reply	other threads:[~2004-07-30 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 15:55 Andrew Cagney
2004-07-30 14:46 ` Andrew Cagney
2004-07-30 18:56 ` Tom Tromey [this message]
2004-07-31 17:42   ` Andrew Cagney
2004-08-06 16:07   ` 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=87isc575ry.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=cagney@gnu.org \
    --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