From: Ben Elliston <bje@redhat.com>
To: Shehryar Humayun <shehryarhumayunkhan@yahoo.com>
Cc: cgen@sources.redhat.com
Subject: Re: Next Step
Date: Mon, 09 Sep 2002 06:27:00 -0000 [thread overview]
Message-ID: <15740.41420.328461.373181@tooth.toronto.redhat.com> (raw)
In-Reply-To: <20020907035403.49161.qmail@web21201.mail.yahoo.com>
>>>>> "Shehryar" == Shehryar Humayun <shehryarhumayunkhan@yahoo.com> writes:
Shehryar> CGENDIR=@cgendir@ variable still needs a workaround
Shehryar> though. Either you change it manually to your CGEN
Shehryar> source directory or create binutils/cgen and copy all
Shehryar> the source files (*.scm,cpu) into it.
Shehryar> This is due to the fact the value of @cgendir@ is set
Shehryar> to "@srcdir@/../cgen" in <build>/opcodes/Makefile
Shehryar> where srcdir=/root/src/binutils/opcodes/
Shehryar> Am I right?
This is because most people use CGEN in the same source tree as
binutils:
src
\- opcodes
\- bfd
\- libiberty
\- cgen
\- gas
\- etc
Thus, opcodes/Makefile can find the CGEN sources by referring to
../cgen from its own source directory. The directory layout I have
shown above is the one used when checking out `cgen' from the
sources.redhat.com:/cvs/src repository, which is where you should be
getting your sources from (not from the 1.0 release tar file).
Hmm .. I guess it's time for another release?
Ben
prev parent reply other threads:[~2002-09-09 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 2:03 Shehryar Humayun
2002-09-03 7:23 ` Ben Elliston
2002-09-03 20:51 ` Shehryar Humayun
2002-09-03 20:51 ` Shehryar Humayun
2002-09-04 11:11 ` Ben Elliston
2002-09-04 19:42 ` Shehryar Humayun
2002-09-05 2:30 ` Ben Elliston
2002-09-05 16:22 ` Shehryar Humayun
2002-09-06 6:55 ` Ben Elliston
2002-09-06 7:37 ` Problem in opcodes for ARM Shehryar Humayun
2002-09-06 9:02 ` Doug Evans
2002-09-06 11:37 ` Shehryar Humayun
2002-09-06 9:36 ` Next Step Shehryar Humayun
2002-09-06 10:03 ` Ben Elliston
2002-09-06 11:21 ` Shehryar Humayun
2002-09-06 12:07 ` Ben Elliston
2002-09-06 20:54 ` Shehryar Humayun
2002-09-09 6:27 ` 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=15740.41420.328461.373181@tooth.toronto.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=shehryarhumayunkhan@yahoo.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).