All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: 3.1.x and 3.2.x releases
Date: Sat, 29 Dec 2007 01:04:43 +0200	[thread overview]
Message-ID: <200712290104.47070.caglar@pardus.org.tr> (raw)
In-Reply-To: <20071228154704.GA20680@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]

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 :)

-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

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

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

      parent reply	other threads:[~2007-12-28 23:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 16:00 3.1.x and 3.2.x releases Keir Fraser
2007-12-19 17:22 ` Dan Magenheimer
2007-12-20 10:26   ` Keir Fraser
2007-12-26 19:53     ` Dan Magenheimer
2007-12-26 23:08       ` Keir Fraser
2007-12-28 22:52         ` Dan Magenheimer
2007-12-29  9:18           ` Keir Fraser
2007-12-29  9:21             ` Keir Fraser
2008-01-03 17:24               ` Dan Magenheimer
2007-12-19 18:34 ` John Levon
2007-12-20  3:58 ` You, Yongkang
2007-12-20  5:02   ` John Levon
2007-12-27 23:37 ` S.Çağlar Onur
2007-12-28  8:38   ` Keir Fraser
2007-12-28 10:17     ` S.Çağlar Onur
2007-12-28 13:16       ` Keir Fraser
2007-12-28 14:55         ` John Levon
2007-12-28 15:19           ` Keir Fraser
2007-12-29  1:18           ` Ryan Scott
2007-12-28 15:47         ` Daniel P. Berrange
2007-12-28 16:00           ` Keir Fraser
2008-01-01 16:31             ` S.Çağlar Onur
2008-01-06 22:50               ` Keir Fraser
2007-12-28 23:04           ` S.Çağlar Onur [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712290104.47070.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=berrange@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.