qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: check for EFD_NONBLOCK | EFD_CLOEXEC flags
Date: Mon, 21 Nov 2011 18:22:30 -0600	[thread overview]
Message-ID: <4ECAEB46.1000702@codemonkey.ws> (raw)
In-Reply-To: <1321836898-22078-1-git-send-email-jcmvbkbc@gmail.com>

On 11/20/2011 06:54 PM, Max Filippov wrote:
> Add check for the EFD_NONBLOCK and EFD_CLOEXEC flags to the
> CONFIG_EVENTFD test.
> This fixes the following build failure on Fedora 9:
>
>        CC    event_notifier.o
>      event_notifier.c: In function `event_notifier_init':
>      event_notifier.c:21: error: `EFD_NONBLOCK' undeclared (first use in this function)
>      event_notifier.c:21: error: (Each undeclared identifier is reported only once
>      event_notifier.c:21: error: for each function it appears in.)
>      event_notifier.c:21: error: `EFD_CLOEXEC' undeclared (first use in this function)
>      make: *** [event_notifier.o] Error 1
>
> Signed-off-by: Max Filippov<jcmvbkbc@gmail.com>

Applied.  Thanks.

Regards,

Anthony Liguori

> ---
>   configure |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure b/configure
> index 6c77fbb..580cd4d 100755
> --- a/configure
> +++ b/configure
> @@ -2200,7 +2200,7 @@ cat>  $TMPC<<  EOF
>
>   int main(void)
>   {
> -    int efd = eventfd(0, 0);
> +    int efd = eventfd(0, EFD_NONBLOCK | EFD_CLOEXEC);
>       return 0;
>   }
>   EOF

      parent reply	other threads:[~2011-11-22  0:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  0:54 [Qemu-devel] [PATCH] configure: check for EFD_NONBLOCK | EFD_CLOEXEC flags Max Filippov
2011-11-21 10:29 ` Stefan Hajnoczi
2011-11-22  0:22 ` Anthony Liguori [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=4ECAEB46.1000702@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jcmvbkbc@gmail.com \
    --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 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).