From: Don Slutz <dslutz@verizon.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.3.2-rc1 and 4.2.4-rc1 have been tagged
Date: Fri, 07 Feb 2014 17:04:42 -0500 [thread overview]
Message-ID: <52F5587A.4010608@terremark.com> (raw)
In-Reply-To: <52E8F6B30200007800117E35@nat28.tlf.novell.com>
On 01/29/14 06:40, Jan Beulich wrote:
> All,
>
> aiming at releases with, as before, presumably just one more RC on
> each of them, please test!
Tested 4.3.2-rc1 on CentOS 5.10 and Fedora 17.
CentOS 5.10 has a build issue with QEMU:
http://lists.xen.org/archives/html/xen-devel/2014-02/msg00084.html
Has more info, for this testing I changed:
Author: Don Slutz <dslutz@verizon.com>
Date: Fri Jan 31 22:37:04 2014 +0000
Work around QEMU bug #1257099 on CentOS 5.10
diff --git a/tools/Makefile b/tools/Makefile
index e44a3e9..b411e60 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -187,7 +187,7 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
source=.; \
fi; \
cd qemu-xen-dir; \
- $$source/configure --enable-xen --target-list=i386-softmmu \
+ $$source/configure --enable-xen --target-list=i386-softmmu
--disable-smartcard-nss\
--prefix=$(PREFIX) \
--source-path=$$source \
--extra-cflags="-I$(XEN_ROOT)/tools/include \
and was able to use the resulting build for some simple testing. No new
issues were found.
-Don Slutz
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-02-07 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52E7D3BB02000078001179F5@nat28.tlf.novell.com>
2014-01-29 11:40 ` Xen 4.3.2-rc1 and 4.2.4-rc1 have been tagged Jan Beulich
2014-02-07 22:04 ` Don Slutz [this message]
2014-02-10 7:38 ` Jan Beulich
2014-02-10 15:04 ` Stefano Stabellini
2014-02-10 23:07 ` Don Slutz
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=52F5587A.4010608@terremark.com \
--to=dslutz@verizon.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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).