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] The most recent attempt to build 2.6.29-rc8

To: M A Young <m.a.young@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 25 Mar 2009 10:28:11 -0700
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 25 Mar 2009 10:29:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.GSO.2.00.0903250840210.2991@xxxxxxxxxxxxxxxx>
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>
References: <276529.49208.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.LFD.2.00.0903222118560.12845@xxxxxxxxxxxxxxx> <49C9E9AC.8070907@xxxxxxxx> <alpine.GSO.2.00.0903250840210.2991@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (X11/20090320)
M A Young wrote:
That's strange because it wasn't when I sent it. I wonder if it got mangled in-transit.

It was an attachment, so it should have been resistant. Though it also had a '\0' on the end for good measure.

Unfortunately this didn't help me; it still ended up making this 'm', which doesn't work. The simple fix is, I think, to make this a "bool", so it gets built in. Its not really big enough to bother with.

I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so it didn't cause me a problem, though of course if any of the dependent modules were "y" then that would indeed be incorrect. I did have an alternate way of doing it that I could try.

Hm. I wonder if there's a bunch of symbol exports missing. Or perhaps it's a secondary problem, like mkinitrd is not putting the right modules in place.

   J

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