From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Martinx - <thiagocmartinsc@gmail.com>,
Xen List <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] Re: Xen 4.0.1 failed to compile on Ubuntu Natty 32 bits
Date: Mon, 10 Jan 2011 11:23:05 +0100 [thread overview]
Message-ID: <20110110102305.GB4915@aepfle.de> (raw)
In-Reply-To: <19730.10439.580674.373657@mariner.uk.xensource.com>
On Wed, Dec 22, Ian Jackson wrote:
> Martinx - ¸§¼àº writes ("Re: [Xen-devel] Re: Xen 4.0.1 failed to compile on Ubuntu Natty 32 bits"):
> > Here is the patch to run "make xen ; make tools" from xen-4.0.1.tar.gz
> > source on top of Ubuntu 11.04:
>
> I've been sort of following this conversation. How much of this do
> you think ought to be in xen-4.0-testing ? I ask because a big part
> of this change is to sort out the ordering of a linker command line,
> and we already have a much bigger change to do this in xen-unstable.hg
> (which will become Xen 4.1).
> Bear in mind that Xen 4.1 will be out early next year, and already has
> at least the link link ordering fix.
Looking at their website at https://wiki.ubuntu.com/NattyReleaseSchedule
indicates that Xen 4.1 and their 11.04 release overlap.
So those who compile from source could also use the 4.1 release.
Olaf
prev parent reply other threads:[~2011-01-10 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 22:09 Xen 4.0.1 failed to compile on Ubuntu Natty 32 bits Martinx - ジェームズ
2010-12-10 23:04 ` Martinx - ジェームズ
2010-12-15 22:15 ` Martinx - ジェームズ
2010-12-15 22:21 ` Martinx - ジェームズ
2010-12-16 9:34 ` [Xen-devel] " Ian Campbell
2010-12-16 17:27 ` Martinx - ジェームズ
2010-12-16 17:36 ` Olaf Hering
2010-12-16 19:02 ` [Xen-devel] " Martinx - ジェームズ
2010-12-16 19:16 ` Olaf Hering
2010-12-16 20:21 ` Martinx - ジェームズ
2010-12-22 16:35 ` [Xen-devel] " Ian Jackson
2011-01-10 10:23 ` Olaf Hering [this message]
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=20110110102305.GB4915@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=thiagocmartinsc@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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.