WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Building unmodified_drivers fails in unstable x64 XEN

To: "Nowatzki, Thomas L" <Thomas.Nowatzki@xxxxxxxxxx>
Subject: Re: [Xen-devel] Building unmodified_drivers fails in unstable x64 XEN
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Mon, 13 Nov 2006 15:10:25 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 13 Nov 2006 07:12:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <19D0D50E9B1D0A40A9F0323DBFA04ACC03FC4904@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <19D0D50E9B1D0A40A9F0323DBFA04ACC03FC4904@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2006-11-09 at 08:03 -0600, Nowatzki, Thomas L wrote:
> Per the instructions in the README I am trying to build the
> paravirtualized drivers from unmodified_drivers.  However, it doesn't
> seem to work in the latest unstable XEN version.  I am running SLES10
> x64 version.  Quite possibly I am doing the build incorrectly although
> it seems quite straight forward:

> include/xen/interface/xen-compat.h:23:2: error: #error "These header
> files do not support the requested interface version."

I think the problem is that the SLES10 kernel already includes Xen
headers (the 3.0.2 version I guess) which are getting mixed up with the
headers supplied in the unmodified drivers tree. The drivers want to
build against their own versions.

Can you run the build with V=1 to check that this is what is happening,
i.e. I expect -I/usr/src/foo is before -Iunmodified/.../include

Can you also have a look
in /usr/src/linux/include/xen/interface/xen-compat.h to see what
__XEN_LATEST_INTERFACE_VERSION__ is.

I'm not sure what the best solution is, as a work around you could try
renaming the include/xen subtree of the kernel source in /usr/src/linux
out of the way.

Ian.


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