From: Doug Evans <dje@transmeta.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com, wilson@tuliptree.org, fche@redhat.com,
nickc@redhat.com
Subject: Re: regenerating cgen sim sources for gdb 6.0
Date: Fri, 20 Jun 2003 21:16:00 -0000 [thread overview]
Message-ID: <16115.31137.475221.370050@casey.transmeta.com> (raw)
In-Reply-To: <3EF37387.4050605@redhat.com>
Andrew Cagney writes:
> I guess Frank is the obvious person?
Either Frank or Nick.
To regenerate the files
cvs co gdb
cvs co cgen
cd src/cgen
sh gen-all-sim
Figuratively speaking. I haven't tried this precise sequence.
One runs gen-all-sim from the src/cgen directory in a gdb+cgen src tree.
Beyond that, what one does testing-wise before checkin is up to the person
doing the checkin. S/he can certainly feel free to enlist my help.
next prev parent reply other threads:[~2003-06-20 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 16:27 Doug Evans
2003-06-20 18:45 ` Frank Ch. Eigler
2003-06-20 18:54 ` Doug Evans
2003-06-20 19:39 ` Andrew Cagney
2003-06-20 20:25 ` Doug Evans
2003-06-20 20:50 ` Andrew Cagney
2003-06-20 21:16 ` Doug Evans [this message]
2003-06-20 21:22 ` Doug Evans
2003-06-20 16:30 Doug Evans
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=16115.31137.475221.370050@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=ac131313@redhat.com \
--cc=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=wilson@tuliptree.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