From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] Makefile: remoeve duplicate qemu-error.o
Date: Tue, 11 May 2010 13:13:15 +0200 [thread overview]
Message-ID: <cover.1273576209.git.quintela@redhat.com> (raw)
Hi
qemu-error.o appears in several places in Makefile*,
with several combinations of make; make clean; make
you could get a build error. Fix it defining it in a single
place. Once there, just create a shared-obj-y for objects
that are needed for both tools and qemu binary. This should remove
this error in the future.
once there, fix fsdevel to check for CONFIG_LINUX only once instead of 4 times.
Juan Quintela (2):
Create shared-obj-y
state that fsdev depends on LINUX only once
Makefile | 8 +++++---
Makefile.objs | 15 +++++++++------
2 files changed, 14 insertions(+), 9 deletions(-)
next reply other threads:[~2010-05-11 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 11:13 Juan Quintela [this message]
2010-05-11 11:13 ` [Qemu-devel] [PATCH 1/2] Create shared-obj-y Juan Quintela
2010-05-11 11:45 ` Markus Armbruster
2010-05-11 11:52 ` Kevin Wolf
2010-05-11 12:07 ` Markus Armbruster
2010-05-11 12:17 ` [Qemu-devel] " Juan Quintela
2010-05-11 11:13 ` [Qemu-devel] [PATCH 2/2] state that fsdev depends on LINUX only once Juan Quintela
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=cover.1273576209.git.quintela@redhat.com \
--to=quintela@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.