From: Richard Zidlicky <rz@linux-m68k.org>
To: qemu-devel@nongnu.org, fabrice.bellard@free.fr
Subject: [Qemu-devel] [patch] m68k build fixes
Date: Sat, 6 Mar 2004 14:05:23 +0100 [thread overview]
Message-ID: <20040306130523.GA5887@linux-m68k.org> (raw)
Hi,
trivial fixes against current CVS.
Richard
--- qemu-0.5.3/configure.rz Fri Mar 5 14:53:06 2004
+++ qemu-0.5.3/configure Fri Mar 5 20:28:00 2004
@@ -278,8 +278,8 @@
echo "ARCH=ia64" >> $config_mak
echo "#define HOST_IA64 1" >> $config_h
elif test "$cpu" = "m68k" ; then
- echo "ARCH=m68k" >> config.mak
- echo "#define HOST_M68K 1" >> $TMPH
+ echo "ARCH=m68k" >> $config_mak
+ echo "#define HOST_M68K 1" >> $config_h
else
echo "Unsupported CPU"
exit 1
--- qemu-0.5.3/Makefile.target.rz Fri Mar 5 14:52:47 2004
+++ qemu-0.5.3/Makefile.target Fri Mar 5 20:39:22 2004
@@ -35,6 +35,11 @@
endif
endif
+ifeq ($(ARCH), m68k)
+ifdef CONFIG_SOFTMMU
+PROGS+=$(QEMU_SYSTEM)
+endif
+endif
endif
ifeq ($(TARGET_ARCH), ppc)
reply other threads:[~2004-03-06 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040306130523.GA5887@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=fabrice.bellard@free.fr \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).