From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: 3.1.x and 3.2.x releases Date: Fri, 28 Dec 2007 15:47:04 +0000 Message-ID: <20071228154704.GA20680@redhat.com> References: <200712281217.11561.caglar@pardus.org.tr> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: caglar@pardus.org.tr, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|