From: Andrew Cagney <ac131313@ges.redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: gdb@sources.redhat.com
Subject: Re: why cgen/cpu and not cgen in gdb_5_2_1-2002-07-23-release
Date: Wed, 24 Jul 2002 11:49:00 -0000 [thread overview]
Message-ID: <3D3EF6CB.5080300@ges.redhat.com> (raw)
In-Reply-To: <200207241732.KAA00372@casey.transmeta.com>
> I just checked out gdb_5_2_1-2002-07-23-release from the cvs tree.
>
> Question: Why are the cgen cpu files there but not cgen?
Same reason GDB doesn't include autoconf, automake, gettext, bison, and
many other tools used to create generated files. Not needed.
Andrew
next prev parent reply other threads:[~2002-07-24 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 10:32 Doug Evans
2002-07-24 11:49 ` Andrew Cagney [this message]
2002-07-25 20:32 ` Doug Evans
2002-08-01 16:21 ` 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=3D3EF6CB.5080300@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=dje@transmeta.com \
--cc=gdb@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