xen-ia64-devel

[Top] [All Lists]

[Xen-devel] ia64 Linux build breakage

from [Jan Beulich]

[Permanent Link][Original]

To:	<xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] ia64 Linux build breakage
From:	"Jan Beulich" <JBeulich@xxxxxxxxxx>
Date:	Mon, 20 Dec 2010 12:56:11 +0000
Cc:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Mon, 20 Dec 2010 05:08:02 -0800
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Already with the .36 Xen changes, ia64 Linux didn't build anymore when
Xen was enabled in .config. I was about to consolidate and submit a
patch for this, but .37 makes the situation even worse in that it's not
possible anymore to fix this with a couple of simple adjustments like
making includes of non-existing headers conditional or adding a couple
of #ifdef-s here and there.

Is the ia64 Xen code still being considered maintained? If yes - aren't
changes to architecture independent Xen pieces supposed to be
architecture independent? If not - shouldn't ia64's respective config
options then be made dependent on BROKEN?

Thanks, Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] ia64 Linux build breakage, Jan Beulich <=

Indexes:	[Date] [Thread] [Top] [All Lists]