From: Tracy.Kuhrt@microchip.com
To: fche@redhat.com
Cc: cgen@sourceware.cygnus.com
Subject: Re: NEWBIE Question: Generating Source Files
Date: Wed, 04 Oct 2000 08:31:00 -0000 [thread overview]
Message-ID: <OFDAB5AFCF.A91614BF-ON0725696E.00530CD0@microchip.com> (raw)
I did not modify the Makefile.in file. I thought that was generated
automatically from the Makefile.am file with automake. The lines that you
list below do not exist in either my Makefile.am or Makefile.in file for
m32r. Those lines look pretty important :-) I have pulled the latest
version from CVS on sources.redhat.com. This appears to have those lines.
Obviously binutils-2.10 did not come with this version of Makefile.am. I
will give that a shot.
Thanks for your help. I could have been struggling for quite a while over
this.
Tracy
"Frank Ch.
Eigler" To: Tracy.Kuhrt@microchip.com
<fche@redhat. cc: cgen@sourceware.cygnus.com
com> Subject: Re: NEWBIE Question: Generating Source Files
10/04/2000
07:46 AM
Hi -
On Wed, Oct 04, 2000 at 07:47:53AM -0700, Tracy.Kuhrt@microchip.com wrote:
> [...]
> The problem that I am having is generating the source files. I have
modified
> my opcodes/Makefile.am file to duplicate the m32r setup. When I do a
`make
> dep` in the opcodes directory, I am receiving the error:
> make: *** No rule to make target `xx-asm.c', needed by `DEP'. Stop.
> [...]
Perhaps you missed adding a copy of the dependency portions in Makefile.in:
$(srcdir)/m32r-desc.h $(srcdir)/m32r-desc.c $(srcdir)/m32r-opc.h
$(srcdir)/m32r-opc.c $(srcdir)/m32r-ibld.c $(srcdir)/m32r-opinst.c
$(srcdir)/m32r-asm.c $(srcdir)/m32r-dis.c: $(M32R_DEPS)
@true
stamp-m32r: $(CGENDEPS) $(CGENDIR)/m32r.cpu $(CGENDIR)/m32r.opc
$(MAKE) run-cgen arch=m32r prefix=m32r options=opinst
extrafiles=opinst
You could configure with "--enable-cgen-maint", or else use "make
stamp-TARGET"
to rebuild opcodes/ by hand.
- FChE
next reply other threads:[~2000-10-04 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-04 8:31 Tracy.Kuhrt [this message]
2000-10-04 9:03 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2000-10-04 9:51 Tracy.Kuhrt
2000-10-04 10:02 ` Frank Ch. Eigler
2000-10-04 9:12 Tracy.Kuhrt
2000-10-04 9:26 ` Frank Ch. Eigler
2000-10-04 7:41 Tracy.Kuhrt
2000-10-04 7:46 ` Frank Ch. Eigler
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=OFDAB5AFCF.A91614BF-ON0725696E.00530CD0@microchip.com \
--to=tracy.kuhrt@microchip.com \
--cc=cgen@sourceware.cygnus.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).