Re: [Xen-devel] 3.1.x and 3.2.x releases

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 28/12/07 15:47, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:

> On Fri, Dec 28, 2007 at 01:16:50PM +0000, Keir Fraser 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?
> 
> The gnulib stuff is for portability. The stdint.h in the gnulib/ directory
> of libvirt will only be used on OS where there is no stdint.h present in
> the regular /usr/include.
> 
> Can someone tell me what OS / platform the libvirt compile errors were
> occurring on. stdint.h  is a pretty common thing so I'd only expect it
> to be have been used when building libvirt on Windows, certainly not when
> on Linux.

Well, I hopefully fixed it now anyway, both in 3.1-testing and unstable.

 -- Keir



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