Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ben Stanley <bds02@uow.edu.au>
To: gdb mailing list <gdb@sources.redhat.com>
Subject: weekly cvs tarball uses unknown pserver
Date: Thu, 21 Nov 2002 15:27:00 -0000	[thread overview]
Message-ID: <1037921266.20564.20.camel@dragon.home> (raw)


Hi,

I downloaded

gdb+dejagnu-weekly-CVS-5.2.90_20021119.tar.bz2

and unpacked it. It compiles OK, although the problems I reported
previously against gdb 5.2.1 are still present.

However, when I try to update it to current cvs, by first logging in and
then running "cvs update", I receive the following error message:

ben [10:07:11] /share/install/linux/gdb-cvs/src $ cvs update
Unknown host anoncvs.cygnus.com.

It turns out that all of the CVS/Root files contain 

:pserver:anoncvs@anoncvs.cygnus.com:/cvs/src

and the host is unknown to dns. The web page says to use
sources.redhat.com.

Changing all of the Root files to
:pserver:anoncvs@sources.redhat.com:/cvs/src
allows the update to proceed as expected.

Ben.

--
Ben Stanley, PhD candidate
School of Information Technology and Computer Science
University of Wollongong


                 reply	other threads:[~2002-11-21 23:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1037921266.20564.20.camel@dragon.home \
    --to=bds02@uow.edu.au \
    --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