From: Ben Elliston <bje@redhat.com>
To: "龚 源泉" <source_kong@hotmail.com>
Cc: cgen@sources.redhat.com
Subject: Re: a question about doing an opcodes port
Date: Mon, 26 Aug 2002 06:58:00 -0000 [thread overview]
Message-ID: <15722.13305.223829.58878@tooth.toronto.redhat.com> (raw)
In-Reply-To: <F6473lhRxRoJPaxJNuH0001ebee@hotmail.com>
>>>>> "source" == source kong <gb2312> writes:
source> What is the directory "opcodes" in step 8, does it refer to the opcodes
source> directory in the binutils(I have downloaded binutils-2.12 from the gnu
source> ftp)package?
Yes, but the opcodes build directory needs to be configured for your
target, not a native build.
source> What does "Add dependencies to "opcodes/Makefile.am" mean?
See opcodes/Makefile.am and look at, for example, the fr30 port.
Mimic what was done for that port.
source> What are the eight opcodes files?
In the case of the fr30 port:
fr30-asm.c fr30-desc.h fr30-ibld.c fr30-opc.h
fr30-desc.c fr30-dis.c fr30-opc.c
source> By the way, could you please give me an explanation about
source> port?
What kind of explanation are you looking for, specifically?
Cheers, Ben
prev parent reply other threads:[~2002-08-26 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 0:21 龚 源泉
2002-08-26 6:58 ` Ben Elliston [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=15722.13305.223829.58878@tooth.toronto.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=source_kong@hotmail.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).