From: Shehryar Humayun <shehryarhumayunkhan@yahoo.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: Next Step
Date: Fri, 06 Sep 2002 09:36:00 -0000 [thread overview]
Message-ID: <20020906163633.2209.qmail@web21201.mail.yahoo.com> (raw)
In-Reply-To: <15736.46038.217700.778062@tooth.toronto.redhat.com>
Hi,
After configuring build directory for m32r-elf, this
is what I get:
>make -C root/build/opcodes/ stamp-m32r
make: Entering directory 'root/build/opcodes/'
make: no rule to make target '../cgen/stamp-cgen',
needed by 'stamp-m32r'. Stop
make: Leaving directory 'root/build/opcodes/'
If we have a look at stamp-m32r in
src/opcodes/Makefile.in and build/opcodes/Makefile,
stamp-m32r: $(CGENDEPS) $(CPUDIR)/m32r.cpu
$(CPUDIR)/m32r.opc
$(MAKE) run-cgen arch=m32r prefix=m32r options=opinst
extrafiles=opinst
CGENDEPS = ../cgen/stamp-cgen \
$(CGENDIR)/desc.scm $(CGENDIR)/desc-cpu.scm \ ...
remain the same for both source and build Makefiles.
I think this is what might be causing the problem in
build/opcodes/Makefile:
cgendir = $(srcdir)/../cgen
CGENDIR = $(srcdir)/../cgen
Please correct me where I am wrong, doesn't
"cgendir=$(srcdir)/../cgen" mean that cgen source
directory (containing .scm/.cpu files) has to be
present in binutils-2.12 source tree at the same level
as is opcodes directory? I mean to say that as
"binutils-2.12/opcodes" exist, so should
"binutils-2.12/cgen", no? Is this the cause of having
message "No rule to make target ..."?
Regards
Shehryar
--- Ben Elliston <bje@redhat.com> wrote:
> Check out the GNU
> binutils source code, configure it for m32r-elf and
> then:
>
> make -C <build>/opcodes stamp-m32r
>
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
next prev parent reply other threads:[~2002-09-06 16:36 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-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 ` Shehryar Humayun [this message]
2002-09-06 10:03 ` Next Step 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
2002-09-03 20:51 ` Shehryar Humayun
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=20020906163633.2209.qmail@web21201.mail.yahoo.com \
--to=shehryarhumayunkhan@yahoo.com \
--cc=bje@redhat.com \
--cc=cgen@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).