This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Fix 64-bit foreign header check

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix 64-bit foreign header check
From: John Levon <john.levon@xxxxxxx>
Date: Wed, 15 Aug 2007 17:08:23 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Aug 2007 09:07:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2E8E29E.143F3%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070815152705.GA9299@xxxxxxxxxxxxxxxxx> <C2E8E29E.143F3%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Wed, Aug 15, 2007 at 05:04:30PM +0100, Keir Fraser wrote:

> > There is no such "32-bit" environment, we can always produce both.  What
> > you're
> > suggesting sounds like a cross-compile. This is absolutely not a cross
> > compile;
> > in particular we can and do want this header check to happen.
> > 
> > We set XEN_COMPILE_ARCH by hand to 64-bit since the Xen makefiles have the
> > notion
> > that uname has anything to do with 32 or 64 bitness (a Linux-ism; in fact an
> > x86_64-Linux-ism, since I believe other Linux arches do it the traditional
> > way).
> Hmmm... Well varying COMPILE_ARCH when the compile arch is not actually
> changing seems dodgy to me.
> In any case, binaries that run on the compile host should build with
> HOSTCC/HOSTCFLAGS. That seems a pretty simple and obvious rule that I do not
> want to introduce exceptions to.

Can you please explain what you want us to do.


Xen-devel mailing list