Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb@sources.redhat.com
Subject: Re: Current snapshot
Date: Mon, 03 Feb 2003 01:35:00 -0000	[thread overview]
Message-ID: <15933.51310.38055.88189@localhost.redhat.com> (raw)
In-Reply-To: <15933.41183.54378.465447@nick.uklinux.net>

Nick Roberts writes:
 > 
 > I've downloaded the current snapshot (it was gdb+dejagnu-20030201.tar.bz2),
 > uncompressed, unpacked and built gdb without any problem.
 > 
 > I'm ready to receive the imminent patches for:
 > 
 > interpreter mi -<mi-command> <mi-args> 
 > -interpreter-exec console cli-command
 > 
 > http://sources.redhat.com/gdb/current/ says
 > 
 > > Once you have downloaded and unpacked this snapshot, you can cd to the src
 > > directory and use the command:
 > 
 > > cvs update
 > 
 > > to bring your sources up-to-date (see note above about login).
 > 
 > I can't find the src directory. The directory that appears to contain the
 > sources is gdb and there are no directories called CVS or files called Root,
 > Entries anywhere etc. So when I type cvs update, I get
 > 
 > > cvs update: No CVSROOT specified!  Please use the `-d' option
 > > cvs [update aborted]: or set the CVSROOT environment variable.
 > 
 > Can anyone help please?
 > 

Instead of downloading a snapshot, which doesn't have the CVS stuff in it,
do a cvs checkout as explained in http://sources.redhat.com/gdb/current/

then, all you will have to do is a 'cvs update' to get the patches.

elena


 > Nick


  reply	other threads:[~2003-02-03  1:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:53 Nick Roberts
2003-02-03  1:35 ` Elena Zannoni [this message]
2003-02-03  6:44   ` 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=15933.51310.38055.88189@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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