All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org
Subject: [PATCH 1 of 2] Fix building of kvmtrace tool for all archs
Date: Thu, 12 Jun 2008 16:17:45 +0000	[thread overview]
Message-ID: <d3bd00830ce98396c7ee.1213287465@thinkpadL> (raw)
In-Reply-To: <patchbomb.1213287464@thinkpadL>

2 files changed, 2 insertions(+), 1 deletion(-)
user/Makefile              |    2 ++
user/config-x86-common.mak |    1 -


$(kvmtrace_objs) is defined in config-x86-common.mak. This needs to be moved to the common Makefile so everyone can build it. Also it is just one c file as opposed to multiple diffrering c files as with kvmctl.

Signed-off-by: Jerone Young <jyoung5@us.ibm.com>

diff --git a/user/Makefile b/user/Makefile
--- a/user/Makefile
+++ b/user/Makefile
@@ -33,6 +33,8 @@ autodepend-flags = -MMD -MF $(dir $*).$(
 
 LDFLAGS += -pthread -lrt
 
+kvmtrace_objs= kvmtrace.o
+
 kvmctl: $(kvmctl_objs)
 	$(CC) $(LDFLAGS) $^ -o $@
 
diff --git a/user/config-x86-common.mak b/user/config-x86-common.mak
--- a/user/config-x86-common.mak
+++ b/user/config-x86-common.mak
@@ -3,7 +3,6 @@ all: kvmctl kvmtrace test_cases
 all: kvmctl kvmtrace test_cases
 
 kvmctl_objs= main.o iotable.o ../libkvm/libkvm.a
-kvmtrace_objs= kvmtrace.o
 balloon_ctl: balloon_ctl.o
 
 FLATLIBS = $(TEST_DIR)/libcflat.a $(libgcc)

WARNING: multiple messages have this Message-ID (diff)
From: Jerone Young <jyoung5@us.ibm.com>
To: kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org
Subject: [PATCH 1 of 2] Fix building of kvmtrace tool for all archs
Date: Thu, 12 Jun 2008 11:17:45 -0500	[thread overview]
Message-ID: <d3bd00830ce98396c7ee.1213287465@thinkpadL> (raw)
In-Reply-To: <patchbomb.1213287464@thinkpadL>

2 files changed, 2 insertions(+), 1 deletion(-)
user/Makefile              |    2 ++
user/config-x86-common.mak |    1 -


$(kvmtrace_objs) is defined in config-x86-common.mak. This needs to be moved to the common Makefile so everyone can build it. Also it is just one c file as opposed to multiple diffrering c files as with kvmctl.

Signed-off-by: Jerone Young <jyoung5@us.ibm.com>

diff --git a/user/Makefile b/user/Makefile
--- a/user/Makefile
+++ b/user/Makefile
@@ -33,6 +33,8 @@ autodepend-flags = -MMD -MF $(dir $*).$(
 
 LDFLAGS += -pthread -lrt
 
+kvmtrace_objs= kvmtrace.o
+
 kvmctl: $(kvmctl_objs)
 	$(CC) $(LDFLAGS) $^ -o $@
 
diff --git a/user/config-x86-common.mak b/user/config-x86-common.mak
--- a/user/config-x86-common.mak
+++ b/user/config-x86-common.mak
@@ -3,7 +3,6 @@ all: kvmctl kvmtrace test_cases
 all: kvmctl kvmtrace test_cases
 
 kvmctl_objs= main.o iotable.o ../libkvm/libkvm.a
-kvmtrace_objs= kvmtrace.o
 balloon_ctl: balloon_ctl.o
 
 FLATLIBS = $(TEST_DIR)/libcflat.a $(libgcc)

  reply	other threads:[~2008-06-12 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 16:17 [PATCH 0 of 2] Enable other archs to build kvmtrace tool Jerone Young
2008-06-12 16:17 ` Jerone Young
2008-06-12 16:17 ` Jerone Young [this message]
2008-06-12 16:17   ` [PATCH 1 of 2] Fix building of kvmtrace tool for all archs Jerone Young
2008-06-12 16:17 ` [PATCH 2 of 2] kvmtrace tool build by default for powerpc Jerone Young
2008-06-12 16:17   ` Jerone Young

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=d3bd00830ce98396c7ee.1213287465@thinkpadL \
    --to=jyoung5@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.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.