From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Cc: Anthony Green <green@moxielogic.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCH] moxie: fix compilation with CONFIG_FDT
Date: Sun, 24 Mar 2013 01:45:22 +0100 [thread overview]
Message-ID: <1364085922-19147-1-git-send-email-aurelien@aurel32.net> (raw)
When CONFIG_FDT is enabled, qemu-system-moxie fails to build with
the following error:
$ make
make[1]: *** No rule to make target `hw/moxie/../device_tree.o', needed by `qemu-system-moxie'. Stop.
make: *** [subdir-moxie-softmmu] Error 2
Since commit 320ba5f, device_tree.o is always linked to the targets. This patch
simply removes it from hw/moxie/Makefile.objs.
Cc: Anthony Green <green@moxielogic.com>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
---
hw/moxie/Makefile.objs | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/moxie/Makefile.objs b/hw/moxie/Makefile.objs
index d0772d1..a5f1742 100644
--- a/hw/moxie/Makefile.objs
+++ b/hw/moxie/Makefile.objs
@@ -1,6 +1,5 @@
# moxie boards
obj-y = serial.o mc146818rtc.o vga.o
-obj-$(CONFIG_FDT) += device_tree.o
obj-y := $(addprefix ../,$(obj-y))
obj-y += moxiesim.o
--
1.7.10.4
reply other threads:[~2013-03-24 0:45 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=1364085922-19147-1-git-send-email-aurelien@aurel32.net \
--to=aurelien@aurel32.net \
--cc=green@moxielogic.com \
--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).