From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cagney@gnu.org, kettenis@gnu.org, gdb@sources.redhat.com
Subject: Re: Trimming the CVS "gdb" module
Date: Fri, 22 Oct 2004 10:09:00 -0000 [thread overview]
Message-ID: <20041021134631.GA13029@nevyn.them.org> (raw)
In-Reply-To: <01c4b72b$Blat.v2.2.2$bd636120@zahav.net.il>
On Thu, Oct 21, 2004 at 07:05:33AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 20 Oct 2004 18:21:13 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Andrew Cagney <cagney@gnu.org>, kettenis@gnu.org,
> > gdb@sources.redhat.com
> >
> > > Can't we copycat what Binutils does? IIRC, it comes with an `intl'
> > > directory under `binutils-X.Y.Z', or at least it used to last time I
> > > looked.
> >
> > Yes, the very same copy we just removed from the GDB distribution.
> > No one has felt motivated enough to update it lately. GCC has an
> > updated copy we could pull.
>
> I didn't mean just the directory contents, I meant primarily the
> configure- and build-time machinery that gets gettext to build and be
> installed together with GDB, so that the installed GDB could use it.
Yes, that's what I meant also. None of that lives under gdb/; it's all
in the top level or within intl/.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-21 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:45 Andrew Cagney
2004-10-08 10:10 ` Eli Zaretskii
2004-10-13 4:52 ` Andrew Cagney
2004-10-13 13:45 ` Eli Zaretskii
2004-10-14 4:48 ` Mark Kettenis
2004-10-14 4:53 ` Eli Zaretskii
2004-10-19 19:55 ` Andrew Cagney
2004-10-19 20:34 ` Eli Zaretskii
2004-10-19 22:55 ` Mark Kettenis
2004-10-20 2:29 ` Eli Zaretskii
2004-10-20 4:52 ` Andrew Cagney
2004-10-20 15:11 ` Eli Zaretskii
2004-10-20 18:29 ` Andrew Cagney
2004-10-20 22:21 ` Eli Zaretskii
2004-10-20 23:25 ` Daniel Jacobowitz
2004-10-21 14:51 ` Eli Zaretskii
2004-10-22 10:09 ` Daniel Jacobowitz [this message]
2004-10-19 18:28 ` 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=20041021134631.GA13029@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@gnu.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