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] Recent changeset breaks Xen/ia64 build

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Recent changeset breaks Xen/ia64 build
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Wed, 12 Oct 2005 08:20:02 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 12 Oct 2005 15:18:43 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXPNiGvS/sr92DFQKWgpIHqxsjPnAACMPVA
Thread-topic: [Xen-devel] Recent changeset breaks Xen/ia64 build
Thanks for the help.  I'm still not clear on how what
changed caused the cascading errors, but discovered
that two arch/ia64/vmx files have included public/xen.h
and removing that include fixes the problem.

I'll change this for the next ia64 push.


> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
> Sent: Wednesday, October 12, 2005 8:11 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Recent changeset breaks Xen/ia64 build
> On 12 Oct 2005, at 14:37, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> > Hmmm... some changeset in -unstable in the last 24 hours has
> > badly broken the Xen/ia64 build.  From the cascade of
> > error messages, I suspect it is type-related.  I'll look
> > into it but if someone could point to the likely culprit,
> > I'd appreciate it.
> I removed u8/u16/u32 etc from the public interfaces and fiddled with 
> xen/types.h at the same time. Perhaps I've managed to break 
> xen/types.h 
> for you?
>   -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>