From: "Robert Cragie" <rcc@jennic.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <sid@sources.redhat.com>
Subject: RE: Can't build sid
Date: Thu, 09 Aug 2001 10:33:00 -0000 [thread overview]
Message-ID: <NDBBLOIOMLKELOJBAPAGKEANCIAA.rcc@jennic.com> (raw)
In-Reply-To: <20010809093545.A5366@redhat.com>
> Hmm. According to "cvs [...] co -c", the opcodes module doesn't exist
> by itself. You could alternatively fetch the "binutils", or even "gdb"
> modules, since you'll probably need those tools to construct/debug the
> programs you might be running on the simulator.
OK - succeeded now. For the record, I fetched the gdb module into the same
tree as sid using
cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/src co gdb
I then had to reconfigure the whole lot and build again from scratch.
Thanks for your help
Robert
prev parent reply other threads:[~2001-08-09 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 4:21 Robert Cragie
2001-08-09 4:42 ` Frank Ch. Eigler
2001-08-09 5:18 ` Robert Cragie
2001-08-09 5:22 ` Frank Ch. Eigler
2001-08-09 5:45 ` Robert Cragie
2001-08-09 6:35 ` Frank Ch. Eigler
2001-08-09 10:33 ` Robert Cragie [this message]
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=NDBBLOIOMLKELOJBAPAGKEANCIAA.rcc@jennic.com \
--to=rcc@jennic.com \
--cc=fche@redhat.com \
--cc=sid@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).