From: Shehryar Humayun <shehryarhumayunkhan@yahoo.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: Running CGEN
Date: Sat, 31 Aug 2002 21:19:00 -0000 [thread overview]
Message-ID: <20020901041915.21511.qmail@web21206.mail.yahoo.com> (raw)
In-Reply-To: <20020831175959.D7281@redhat.com>
Thanks for the reply. One more thing: should binutils
be configured and installed on the system as well to
regenerate, for example, opcodes files in the
gas/opcodes directory, before running "make
stamp-TARGET". If so, should binutils source tree be
configured with "./configure --target=TARGET" before
running "make ..."?
Thanks in advance
Regards
**************************************************
--- "Frank Ch. Eigler" <fche@redhat.com> wrote:
> Hi -
>
> On Sat, Aug 31, 2002 at 08:49:53AM -0700, Shehryar
> Humayun wrote:
> > [...]
> > According to the CGEN FAQ 7.html, I have to build
> my
> > CGEN build directory before running "make
> stamp-m32r".
> > Does this mean that I have to run
> > "./configure --target=m32r"
> > in the opcodes directory available with binutils?
> > [...]
>
> Almost. Actually, you should run the configure
> script
> of the *parent* of the opcodes directory. That
> top-level
> one recursively invokes the configure script of the
> subdirectories.
>
>
> - FChE
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
next prev parent reply other threads:[~2002-09-01 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 8:49 Shehryar Humayun
2002-08-31 15:00 ` Frank Ch. Eigler
2002-08-31 21:19 ` Shehryar Humayun [this message]
2002-09-03 7:40 ` Ben Elliston
-- strict thread matches above, loose matches on Subject: below --
2002-08-25 19:46 Shehryar Humayun
2002-08-26 4:28 ` Ben Elliston
2002-08-26 9:16 ` John Healy
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=20020901041915.21511.qmail@web21206.mail.yahoo.com \
--to=shehryarhumayunkhan@yahoo.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).