From: Juan Quintela <quintela@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Xen build broken with current git head
Date: Tue, 30 Jun 2009 16:28:00 +0200 [thread overview]
Message-ID: <m3my7pbxu7.fsf@neno.mitica> (raw)
In-Reply-To: <4A49DA07.5070905@redhat.com> (Gerd Hoffmann's message of "Tue\, 30 Jun 2009 11\:25\:27 +0200")
Gerd Hoffmann <kraxel@redhat.com> wrote:
> On 06/30/09 11:09, Jan Kiszka wrote:
>> FYI (sorry, no time to dig into this).
>
> Noticed too. Looks like it tries to build xen on arm now, then fails
> to link. I suspect it's somewhere in the Makefile changes.
Anthony, please apply.
It compiles for me now.
>From 5e5cff8bd81a247f8c13ef9c5ad259a816c66f89 Mon Sep 17 00:00:00 2001
Message-Id: <5e5cff8bd81a247f8c13ef9c5ad259a816c66f89.1246371970.git.quintela@redhat.com>
From: Juan Quintela <quintela@redhat.com>
Date: Tue, 30 Jun 2009 16:25:51 +0200
Subject: [PATCH] fix XEN Build
I miss s/yes/y/ in one place
---
Makefile.target | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile.target b/Makefile.target
index cd7bf35..5a4c406 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -543,7 +543,7 @@ endif
# xen backend driver support
obj-$(CONFIG_XEN) += xen_machine_pv.o xen_domainbuild.o
-ifeq ($(CONFIG_XEN), yes)
+ifeq ($(CONFIG_XEN), y)
LIBS += $(XEN_LIBS)
endif
--
1.6.2.2
next prev parent reply other threads:[~2009-06-30 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:09 [Qemu-devel] Xen build broken with current git head Jan Kiszka
2009-06-30 9:25 ` [Qemu-devel] " Gerd Hoffmann
2009-06-30 14:18 ` Juan Quintela
2009-06-30 14:28 ` Juan Quintela [this message]
2009-06-30 14:32 ` Anthony Liguori
2009-06-30 14:50 ` 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=m3my7pbxu7.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@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.