From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] Unable to run eventfd test, even the libaio-dev installed on debian 10.
Date: Thu, 31 Oct 2019 05:53:40 -0400 (EDT) [thread overview]
Message-ID: <246485198.9905451.1572515620925.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <tencent_28D2BF821D50F4EC33C1EF97@qq.com>
----- Original Message -----
> Thanks for your reply!
> After I check the config.log, I think all check go into the right place, but
> confdefs.h didn't show up, it's sort of weird.
> Some output from config.log:
> configure:6159: checking libaio.h usability
> configure:6159: gcc -c -g -O2 -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:6159: $? = 0
> configure:6159: result: yes
> configure:6159: checking libaio.h presence
> configure:6159: gcc -E -D_FORTIFY_SOURCE=2 conftest.c
> configure:6159: $? = 0
> configure:6159: result: yes
> configure:6159: checking for libaio.h
> configure:6159: result: yes
> configure:6170: checking for io_setup in -laio
> configure:6195: gcc -o conftest -g -O2 -D_FORTIFY_SOURCE=2 conftest.c -laio
> >&5
> configure:6195: $? = 0
> configure:6204: result: yes
> configure:6218: checking io_set_eventfd is defined in aio library or aio
> header
Above looks OK. Please do also "make clean" on everything, just to be sure
you're not using old binaries. I don't see eventfd01 being rebuilt in your
first email.
next prev parent reply other threads:[~2019-10-31 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 9:26 [LTP] Unable to run eventfd test, even the libaio-dev installed on debian 10 limingyu
2019-10-31 9:36 ` Jan Stancek
2019-10-31 9:46 ` limingyu
2019-10-31 9:53 ` Jan Stancek [this message]
[not found] ` <tencent_01F277DA0DC3756E3C6BE5D9@qq.com>
2019-10-31 14:08 ` Jan Stancek
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=246485198.9905451.1572515620925.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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.