24 messages in com.xensource.lists.xen-develRe: [Xen-devel] 3.1.x and 3.2.x releases
FromSent OnAttachments
Keir Fraser19 Dec 2007 08:00 
Dan Magenheimer19 Dec 2007 09:22 
John Levon19 Dec 2007 10:34 
You, Yongkang19 Dec 2007 19:58 
John Levon19 Dec 2007 21:02 
Keir Fraser20 Dec 2007 02:25 
Dan Magenheimer26 Dec 2007 11:52 
Keir Fraser26 Dec 2007 15:07 
S.Çağlar Onur27 Dec 2007 15:37 
Keir Fraser28 Dec 2007 00:38 
S.Çağlar Onur28 Dec 2007 02:16 
Keir Fraser28 Dec 2007 05:16 
John Levon28 Dec 2007 06:55 
Keir Fraser28 Dec 2007 07:18 
Daniel P. Berrange28 Dec 2007 07:46 
Keir Fraser28 Dec 2007 08:00 
Dan Magenheimer28 Dec 2007 14:51 
S.Çağlar Onur28 Dec 2007 15:04 
Ryan Scott28 Dec 2007 17:17 
Keir Fraser29 Dec 2007 01:18 
Keir Fraser29 Dec 2007 01:21 
S.Çağlar Onur01 Jan 2008 08:31 
Dan Magenheimer03 Jan 2008 09:23 
Keir Fraser06 Jan 2008 14:50 
Subject:Re: [Xen-devel] 3.1.x and 3.2.x releases
From:S.Çağlar Onur (cag@pardus.org.tr)
Date:12/28/2007 03:04:20 PM
List:com.xensource.lists.xen-devel

28 Ara 2007 Cum tarihinde, Daniel P. Berrange şunları yazmıştı:

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.

But i'm try to compile libvirt on Linux which has stdint.h in regular /usr/include :)

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!