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] 3.1.x and 3.2.x releases

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] 3.1.x and 3.2.x releases
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 28 Dec 2007 15:19:03 +0000
Cc: caglar@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 28 Dec 2007 07:12:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071228145540.GA8404@xxxxxxxxxxxxxxxxxxxxxxx>
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: AchJZPqZOS1q/LVYEdyWZAAWy6hiGQ==
Thread-topic: [Xen-devel] 3.1.x and 3.2.x releases
User-agent: Microsoft-Entourage/11.3.6.070618
On 28/12/07 14:55, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> Oh, it's because your stdint.h type definitions are macros rather than
>> typedefs. I believe the C spec requires them to be typedef names (Section
>> 7.18 of the C99 draft spec). It looks like the problem stems from the
>> stdint.h supplied with gnulib, included in libvirt-0.4.0. Why does libvirt
>> require its own stdint.h?
> 
> Note this same bogus header breaks Solaris full stop (I think we have a
> patch for it, but I'm not sure)

Well, we could call the handles uint8, uint16, and so on. That shouldn't
clash in the macro namespace. I'll see how invasive that is.

 -- Keir



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