From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Christian Schoenebeck <qemu_oss@crudebyte.com>,
Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] meson: Declare have_virtfs_proxy_helper in main meson.build
Date: Wed, 20 Jan 2021 17:56:38 +0100 [thread overview]
Message-ID: <79f7eccd-8e7f-1b2c-4bb3-cb972ca10a2c@redhat.com> (raw)
In-Reply-To: <20210120151539.1166252-1-philmd@redhat.com>
On 20/01/21 16:15, Philippe Mathieu-Daudé wrote:
> have_virtfs_proxy_helper is used from docs/meson.build, and can be
> not declared when including it before fsdev/meson.build. This fixes:
>
> ../docs/meson.build:54:2: ERROR: Unknown variable "have_virtfs_proxy_helper".
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> meson.build | 2 ++
> fsdev/meson.build | 1 -
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 3d889857a09..8f5a8b997d3 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1032,6 +1032,8 @@
> libattr.found() and
> libcap_ng.found())
>
> +have_virtfs_proxy_helper = have_virtfs and have_tools
> +
> if get_option('virtfs').enabled()
> if not have_virtfs
> if targetos != 'linux'
> diff --git a/fsdev/meson.build b/fsdev/meson.build
> index 65455a179e5..adf57cc43ed 100644
> --- a/fsdev/meson.build
> +++ b/fsdev/meson.build
> @@ -8,7 +8,6 @@
> ), if_false: files('qemu-fsdev-dummy.c'))
> softmmu_ss.add_all(when: 'CONFIG_LINUX', if_true: fsdev_ss)
>
> -have_virtfs_proxy_helper = have_tools and libattr.found() and libcap_ng.found() and have_virtfs
> if have_virtfs_proxy_helper
> executable('virtfs-proxy-helper',
> files('virtfs-proxy-helper.c', '9p-marshal.c', '9p-iov-marshal.c'),
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-01-20 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:15 [PATCH] meson: Declare have_virtfs_proxy_helper in main meson.build Philippe Mathieu-Daudé
2021-01-20 16:56 ` Paolo Bonzini [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=79f7eccd-8e7f-1b2c-4bb3-cb972ca10a2c@redhat.com \
--to=pbonzini@redhat.com \
--cc=groug@kaod.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).