From: Richard Henderson <rth@twiddle.net>
To: Martin Husemann <martin@duskware.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Git head build problem (popcountl vs. system headers)
Date: Thu, 25 Apr 2013 11:36:50 +0100 [thread overview]
Message-ID: <51790742.1050906@twiddle.net> (raw)
In-Reply-To: <20130425064701.GA9899@mail.duskware.de>
On 2013-04-25 07:47, Martin Husemann wrote:
> I just tried building git HEAD on NetBSD-current and gcc chokes on
> a prototype mismatch for popcountl:
>
> util/hbitmap.c has:
>
> static inline int popcountl(unsigned long l)
> {
> return BITS_PER_LONG == 32 ? ctpop32(l) : ctpop64(l);
> }
>
> while NetBSD's strings.h uses:
>
> unsigned int popcountl(unsigned long) __constfunc;
<strings.h> is the K&R header supplanted by ISO <string.h>.
Is there any good reason that we're including it at all?
r~
next prev parent reply other threads:[~2013-04-25 10:37 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 [this message]
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
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=51790742.1050906@twiddle.net \
--to=rth@twiddle.net \
--cc=martin@duskware.de \
--cc=qemu-devel@nongnu.org \
/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.