From: Keith Seitz <keiths@redhat.com>
To: Marco Werth <Marco.Werth@gmx.de>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: AW: Cygwin and Insight - two files missing
Date: Mon, 27 Jan 2003 22:32:00 -0000 [thread overview]
Message-ID: <1043706956.1502.17.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <1273.1043705028@www52.gmx.net>
On Mon, 2003-01-27 at 14:03, Marco Werth wrote:
> How to grab??
>
> I tried the command shown in the instruction...
> Cvs -z9 -d:pserver:anoncvs@sources.redhat.com:/cvs/src co -r gdb_5_2-branch
> insight+dejagnu
You need to do two things:
$ cvs -d:pserver:anoncvs@sources.redhat.com:/cvs/src login
[enter "anoncvs" as password]
$ cvs -d:pserver:anoncvs@sources.redhat.com:/cvs/src co insight+dejangu
On cygwin, I wouldn't even bother with 5.2 or 5.3. Use CVS head. It's
got the new Tcl/Tk which should be more stable than either 5.2 or 5.3.
(And if it isn't, you can tell us about it! :-)
> While make, an error occurs..
> Error 1 parse error....
Can you post the failure? (build command that failed and error output)
Keith
parent reply other threads:[~2003-01-27 22:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1273.1043705028@www52.gmx.net>]
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=1043706956.1502.17.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=Marco.Werth@gmx.de \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).