From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Cragie <rcc@jennic.com>
Cc: sid@sources.redhat.com
Subject: Re: Can't build sid
Date: Thu, 09 Aug 2001 04:42:00 -0000 [thread overview]
Message-ID: <20010809074149.A20148@redhat.com> (raw)
In-Reply-To: <NDBBLOIOMLKELOJBAPAGKEAHCIAA.rcc@jennic.com>
Hi -
On Thu, Aug 09, 2001 at 12:21:23PM +0100, Robert Cragie wrote:
: I am trying to build SID, CVS version checked out at approx. 9th August 2001
: 0900 GMT, and I get the following error.
: [...]
: ../../../../../src/sid/component/cgen-cpu/arm7t/arm7f.cxx:8:
: ../../../../../src/sid/component/cgen-cpu/arm7t/../cgen-cpu.h:27: dis-asm.h:
: No such file or directory
: [...]
This is most likely because you didn't have a newly required sibling directory,
src/opcodes/ checked out beside src/sid/. sid is being taught how to do
on-the-fly disassembly of instructions it is executing, by calling into the
gnu opcodes library. (The opcodes library is shared by the gnu assembler,
disassembler tools, and the debugger, and handles individual
machine language <-> assembly language instruction translations.)
We are in the process of revamping the details of this mechanism, by the way.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD4DBQE7cnb9VZbdDOm/ZT0RAum3AJYxtf0yu252dhthOCxFXYpZ9vCTAJ9BFEpc
NRxZ1hkWO4Vy7iwo364TcQ==
=Zam+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-08-09 4:42 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 [this message]
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
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=20010809074149.A20148@redhat.com \
--to=fche@redhat.com \
--cc=rcc@jennic.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).