From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v4 03/18] meson: require liburing >= 0.3
Date: Wed, 15 Dec 2021 12:27:43 +0100 [thread overview]
Message-ID: <977ffa85-1f5f-7493-cb05-5e2024e3c017@redhat.com> (raw)
In-Reply-To: <20211124130150.268230-4-berrange@redhat.com>
Cc'ing Stefan & Stefano.
On 11/24/21 14:01, Daniel P. Berrangé wrote:
> openSUSE Leap 15.2 ships with liburing == 0.2 against which QEMU fails
> to build.
>
> ../util/fdmon-io_uring.c: In function ‘fdmon_io_uring_need_wait’:
> ../util/fdmon-io_uring.c:305:9: error: implicit declaration of function ‘io_uring_sq_ready’; did you mean ‘io_uring_cq_ready’? [-Werror=implicit-function-declaration]
> if (io_uring_sq_ready(&ctx->fdmon_io_uring)) {
> ^~~~~~~~~~~~~~~~~
> io_uring_cq_ready
>
> This method was introduced in liburing 0.3, so set that as a minimum
> requirement.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> meson.build | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index e2d38a43e6..04d36bf47e 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -427,7 +427,8 @@ if not get_option('linux_aio').auto() or have_block
> endif
> linux_io_uring = not_found
> if not get_option('linux_io_uring').auto() or have_block
> - linux_io_uring = dependency('liburing', required: get_option('linux_io_uring'),
> + linux_io_uring = dependency('liburing', version: '>=0.3',
> + required: get_option('linux_io_uring'),
> method: 'pkg-config', kwargs: static_kwargs)
> endif
> libxml2 = not_found
>
next prev parent reply other threads:[~2021-12-15 11:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 13:01 [PATCH v4 00/18] tests/docker: start using libvirt-ci's "lcitool" for dockerfiles Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 01/18] ui: avoid compiler warnings from unused clipboard info variable Daniel P. Berrangé
2021-11-24 13:33 ` Philippe Mathieu-Daudé
2021-12-15 10:22 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 02/18] spice: Update QXLInterface for spice >= 0.15.0 Daniel P. Berrangé
2021-11-24 13:34 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 03/18] meson: require liburing >= 0.3 Daniel P. Berrangé
2021-12-15 11:27 ` Philippe Mathieu-Daudé [this message]
2021-12-15 11:56 ` Philippe Mathieu-Daudé
2021-12-15 13:25 ` Stefan Hajnoczi
2021-12-15 13:47 ` Stefano Garzarella
2021-12-15 16:21 ` Li Zhang
2021-11-24 13:01 ` [PATCH v4 04/18] ui: avoid warnings about directdb on Alpine / musl libc Daniel P. Berrangé
2021-11-24 13:32 ` Thomas Huth
2021-11-24 13:42 ` Daniel P. Berrangé
2021-12-15 11:59 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 05/18] ci: explicitly skip I/O tests on alpine Daniel P. Berrangé
2021-11-24 13:36 ` Thomas Huth
2021-11-24 13:38 ` Philippe Mathieu-Daudé
2021-11-24 13:46 ` Daniel P. Berrangé
2021-12-15 12:02 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 06/18] tests/docker: switch fedora image to release 35 Daniel P. Berrangé
2021-12-15 11:28 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 07/18] tests: integrate lcitool for generating build env manifests Daniel P. Berrangé
2021-12-15 11:45 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 08/18] tests/docker: auto-generate centos8.docker with lcitool Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 09/18] tests/docker: auto-generate fedora.docker " Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 10/18] tests/docker: auto-generate ubuntu1804.docker " Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 11/18] tests/docker: auto-generate ubuntu2004.docker " Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 12/18] tests/docker: auto-generate opensuse-leap.docker " Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 13/18] tests/docker: remove ubuntu.docker container Daniel P. Berrangé
2021-11-24 13:01 ` [PATCH v4 14/18] .gitlab-ci.d/cirrus: auto-generate variables with lcitool Daniel P. Berrangé
2021-12-15 11:36 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 15/18] tests/docker: updates to alpine package list Daniel P. Berrangé
2021-12-15 11:31 ` Philippe Mathieu-Daudé
2021-12-15 11:43 ` Daniel P. Berrangé
2021-12-15 11:47 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 16/18] tests/docker: fix sorting of alpine image package lists Daniel P. Berrangé
2021-11-24 13:39 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 17/18] tests/docker: fully expand the alpine package list Daniel P. Berrangé
2021-12-15 11:32 ` Philippe Mathieu-Daudé
2021-11-24 13:01 ` [PATCH v4 18/18] tests/docker: auto-generate alpine.docker with lcitool Daniel P. Berrangé
2021-11-24 13:42 ` Philippe Mathieu-Daudé
2021-12-15 12:57 ` [PATCH v4 00/18] tests/docker: start using libvirt-ci's "lcitool" for dockerfiles Daniel P. Berrangé
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=977ffa85-1f5f-7493-cb05-5e2024e3c017@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).