From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] meson: always include contrib/libvhost-user
Date: Sun, 8 Nov 2020 16:54:30 +0100 [thread overview]
Message-ID: <21c2fe85-1715-772e-e1f6-fbbf8157fcbe@redhat.com> (raw)
In-Reply-To: <20201106210340.698771-1-stefanha@redhat.com>
On 11/6/20 10:03 PM, Stefan Hajnoczi wrote:
> libvhost-user is needed when CONFIG_LINUX is set. The CONFIG_VHOST_USER
> check in meson.build is incorrect.
>
> In fact, no explicit check is needed since this dependency is not built
> by default. If something declares a dependency on libvhost-user then it
> will be built, otherwise it won't be built (i.e. on non-Linux hosts).
>
> This fixes ./configure --disable-vhost-user && make.
>
> Fixes: bc15e44cb2191bbb2318878acdf5038134e56394 ("configure: introduce --enable-vhost-user-blk-server")
> Reported-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Reported-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> meson.build | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index f5175010df..b473620321 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1450,11 +1450,7 @@ trace_events_subdirs += [
> 'util',
> ]
>
> -vhost_user = not_found
> -if 'CONFIG_VHOST_USER' in config_host
> - subdir('contrib/libvhost-user')
> -endif
> -
> +subdir('contrib/libvhost-user')
I haven't reviewed what this code does, but testing it I see:
$ ../configure --disable-vhost-user
vhost-user support: YES
which doesn't look correct...
> subdir('qapi')
> subdir('qobject')
> subdir('stubs')
>
next prev parent reply other threads:[~2020-11-08 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 21:03 [PATCH] meson: always include contrib/libvhost-user Stefan Hajnoczi
2020-11-07 8:53 ` Michael S. Tsirkin
2020-11-08 15:54 ` Philippe Mathieu-Daudé [this message]
2020-11-09 9:01 ` Thomas Huth
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=21c2fe85-1715-772e-e1f6-fbbf8157fcbe@redhat.com \
--to=philmd@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).