From: Martin Husemann <martin@duskware.de>
To: Richard Henderson <rth@twiddle.net>
Cc: Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Git head build problem (popcountl vs. system headers)
Date: Sat, 27 Apr 2013 20:50:19 +0200 [thread overview]
Message-ID: <20130427185019.GA9189@mail.duskware.de> (raw)
In-Reply-To: <20130425183655.GA983@mail.duskware.de>
On Thu, Apr 25, 2013 at 08:36:55PM +0200, Martin Husemann wrote:
> Ok, I can fix the namespace issue (which is real) easily.
Turns out to be a bit harder: qemu does not define (as far as I can tell)
any restricting macro (_POSIX_C_SOURCE or whatever).
Should it?
Martin
next prev parent reply other threads:[~2013-04-27 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 6:47 [Qemu-devel] Git head build problem (popcountl vs. system headers) Martin Husemann
2013-04-25 10:36 ` Richard Henderson
2013-04-25 13:38 ` Laszlo Ersek
2013-04-25 17:09 ` Richard Henderson
2013-04-25 17:39 ` Eric Blake
2013-04-25 18:36 ` Martin Husemann
2013-04-25 18:48 ` Peter Maydell
2013-04-27 18:50 ` Martin Husemann [this message]
2013-05-05 12:29 ` Blue Swirl
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=20130427185019.GA9189@mail.duskware.de \
--to=martin@duskware.de \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).