From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
Connor Kuehl <ckuehl@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
virtio-fs@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
Mahmoud Mandour <ma.mandourr@gmail.com>
Subject: Re: [PATCH 1/2] meson: Check for seccomp/cap-ng libraries if virtiofsd is enabled
Date: Wed, 28 Apr 2021 09:34:56 -0700 [thread overview]
Message-ID: <15dbfc38-f0ba-65f1-382c-3ce5b961f108@linaro.org> (raw)
In-Reply-To: <20210428144813.417170-2-philmd@redhat.com>
On 4/28/21 7:48 AM, Philippe Mathieu-Daudé wrote:
> seccomp = not_found
> -if not get_option('seccomp').auto() or have_system or have_tools
> +if not get_option('seccomp').auto() or have_system or have_tools or not get_option('virtiofsd').auto()
> seccomp = dependency('libseccomp', version: '>=2.3.0',
> required: get_option('seccomp'),
> method: 'pkg-config', kwargs: static_kwargs)
This construct is wrong, both before and after, as I read it.
not get_option(foo).auto() is true for both enabled and disabled. If disabled,
why are we examining the dependency? If auto, if we have all of the
dependencies we want to enable the feature -- if we don't probe for the
dependency, how can we enable it?
This error seems to be offset by the OR have_* tests, for which the logic also
seems off.
I think the test should have been
if (have_system or have_tools) and
(not get_option('seccomp').disabled() or
not get_option('virtiofsd').disabled())
Then we need to combine the required: argument, probably like
required: get_option('seccomp').enabled() or
get_option('virtiofsd').enabled()
r~
next prev parent reply other threads:[~2021-04-28 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 14:48 [PATCH 0/2] virtiofsd: Meson build fixes Philippe Mathieu-Daudé
2021-04-28 14:48 ` [PATCH 1/2] meson: Check for seccomp/cap-ng libraries if virtiofsd is enabled Philippe Mathieu-Daudé
2021-04-28 15:06 ` Peter Maydell
2021-04-28 15:34 ` Philippe Mathieu-Daudé
2021-04-28 16:34 ` Richard Henderson [this message]
2021-04-28 18:00 ` Philippe Mathieu-Daudé
2021-04-28 18:36 ` Peter Maydell
2021-04-29 7:31 ` Philippe Mathieu-Daudé
2021-04-28 14:48 ` [PATCH 2/2] util/meson: Build iov/hexdump/buffer_is_zero with virtiofsd Philippe Mathieu-Daudé
2021-04-28 14:52 ` Philippe Mathieu-Daudé
2021-04-28 16:38 ` Richard Henderson
2021-04-28 17:56 ` Philippe Mathieu-Daudé
2021-04-28 19:24 ` Richard Henderson
2021-04-28 19:34 ` Philippe Mathieu-Daudé
2021-04-28 15:15 ` [PATCH 0/2] virtiofsd: Meson build fixes Peter Maydell
2021-04-28 16:52 ` Dr. David Alan Gilbert
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=15dbfc38-f0ba-65f1-382c-3ce5b961f108@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=ckuehl@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ma.mandourr@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=virtio-fs@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).