From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [ANNOUNCE] Xen x86 32-bit hypervisor end of life after 4.2
Date: Mon, 10 Sep 2012 18:24:44 +0100 [thread overview]
Message-ID: <CC73E0EC.3E42A%keir.xen@gmail.com> (raw)
In-Reply-To: <20558.7857.884864.696876@mariner.uk.xensource.com>
On 10/09/2012 18:09, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> Keir Fraser writes ("Re: [ANNOUNCE] Xen x86 32-bit hypervisor end of life
> after 4.2"):
>> On 10/09/2012 15:16, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
>>> I will do this but I have a number of other things which need to go
>>> through the autotester's tests of itself, first. I'll let you know
>>> when it's done.
>>
>> A self-aware autotester. :)
>
> As you say.
>
>> Well that's fine. It doesn't have to be done in a huge hurry.
>
> I've been looking into this and have a draft of a suitable change.
> But: can you confirm that typing "make" will still work on a 32-bit
> system and generate a working tools build ? I don't care what
> hypervisor (if any) it builds, but it has to succeed because that's
> how I build the tools for use in 32-bit dom0s.
You want 'make' at the root Makefile to build successfully? If so we can
stub out 32-bit hypervisor only either in that Makefile, or xen/Makefile.
> Ian.
next prev parent reply other threads:[~2012-09-10 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 11:11 [ANNOUNCE] Xen x86 32-bit hypervisor end of life after 4.2 Keir Fraser
2012-09-10 14:00 ` Keir Fraser
2012-09-10 14:16 ` Ian Jackson
2012-09-10 14:23 ` Keir Fraser
2012-09-10 17:09 ` Ian Jackson
2012-09-10 17:24 ` Keir Fraser [this message]
2012-09-11 10:27 ` Ian Jackson
2012-09-11 10:44 ` Keir Fraser
2012-09-11 10:51 ` Jan Beulich
2012-09-11 10:57 ` Keir Fraser
2012-09-10 16:24 ` David Vrabel
2012-09-10 16:55 ` Keir Fraser
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=CC73E0EC.3E42A%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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).