From: Blue Swirl <blauwirbel@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] configure: Make epoll_create1 test work around SPARC glibc bug
Date: Tue, 19 Apr 2011 22:59:07 +0300 [thread overview]
Message-ID: <BANLkTik3Xi_0Std-TXRmDOz=WmxB3YhhXA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik3bYHBHufOzd1D8SAy7G7RjQVH-A@mail.gmail.com>
On Tue, Apr 19, 2011 at 10:48 PM, Peter Maydell
<peter.maydell@linaro.org> wrote:
> On 19 April 2011 20:37, Blue Swirl <blauwirbel@gmail.com> wrote:
>> On Tue, Apr 19, 2011 at 11:57 AM, Peter Maydell
>> <peter.maydell@linaro.org> wrote:
>>> Work around a SPARC glibc bug which caused the epoll_create1 configure
>>> test to wrongly claim that the function was present. Some versions of
>>> SPARC glibc provided the function in the library but didn't declare
>>> it in the include file; the result is that gcc warns about an implicit
>>> declaration but a link succeeds. So we build the configure test with
>>> -Werror to avoid the test passing but then a -Werror qemu build
>>> failing.
>>
>> But then epoll would not be used.
>
> I think that's fine -- on a system which isn't advertising epoll
> in its include files we shouldn't be trying to use it. It might
> be buggy, or not the same function at all, for instance.
>
> Anybody who actually cares about epoll can upgrade their libc :-)
Maybe epoll is not so interesting as madvise.
But the check is not very specific, there could be some unrelated
warning with the headers. How about checking in the compiled file for
for example EPOLLIN, that should give a clear build failure if the
header is missing?
next prev parent reply other threads:[~2011-04-19 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 8:57 [Qemu-devel] [PATCH] configure: Make epoll_create1 test work around SPARC glibc bug Peter Maydell
2011-04-19 19:37 ` Blue Swirl
2011-04-19 19:48 ` Peter Maydell
2011-04-19 19:59 ` Blue Swirl [this message]
2011-04-19 20:16 ` Peter Maydell
2011-04-19 20:36 ` Blue Swirl
2011-04-20 6:53 ` Peter Maydell
2011-04-20 16:31 ` 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='BANLkTik3Xi_0Std-TXRmDOz=WmxB3YhhXA@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).