qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
	qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/3] meson: move vhost_user_blk_server to meson.build
Date: Thu, 12 Nov 2020 10:58:07 +0000	[thread overview]
Message-ID: <20201112105807.GA1445788@stefanha-x1.localdomain> (raw)
In-Reply-To: <c23c7d03-4165-bf11-e730-ffcc53ebd718@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

On Wed, Nov 11, 2020 at 12:54:38PM +0100, Philippe Mathieu-Daudé wrote:
> On 11/11/20 12:44 PM, Philippe Mathieu-Daudé wrote:
> > On 11/11/20 10:41 AM, Philippe Mathieu-Daudé wrote:
> >> On 11/10/20 6:11 PM, Stefan Hajnoczi wrote:
> >>> The --enable/disable-vhost-user-blk-server options were implemented in
> >>> ./configure. There has been confusion about them and part of the problem
> >>> is that the shell syntax used for setting the default value is not easy
> >>> to read. Move the option over to meson where the conditions are easier
> >>> to understand:
> >>>
> >>>   have_vhost_user_blk_server = (targetos == 'linux')
> >>>
> >>>   if get_option('vhost_user_blk_server').enabled()
> >>>       if targetos != 'linux'
> >>>           error('vhost_user_blk_server requires linux')
> >>>       endif
> >>>   elif get_option('vhost_user_blk_server').disabled() or not have_system
> >>>       have_vhost_user_blk_server = false
> >>>   endif
> >>
> >> Something is odd:
> >>
> >> $ ../configure --disable-system --enable-vhost-user-blk-server
> > 
> > I failed when pasting, this misses '--disable-tools' to make sense.
> > 
> > We define in meson.build:
> > 
> >   have_block = have_system or have_tools
> > 
> > Maybe this is the one you want instead of have_system?
> 
> This snippet seems to fix:
> 
> -- >8 --
> --- a/meson.build
> +++ b/meson.build
> @@ -751,6 +751,10 @@
> 
>  has_statx = cc.links(statx_test)
> 
> +if 'CONFIG_VHOST_USER' in config_host and not (have_system or have_tools)
> +    error('vhost-user does not make sense without system or tools
> support enabled')
> +endif
> +
>  have_vhost_user_blk_server = (targetos == 'linux' and
>      'CONFIG_VHOST_USER' in config_host)
> 
> ---
> 
> $ ../configure --disable-system --enable-vhost-user-blk-server
> ../source/qemu/meson.build:755:4: ERROR: Problem encountered: vhost-user
> does not make sense without system or tools support enabled
> 
> I'll send a patch.

This patch was discussed in "[PATCH-for-5.2 v2 0/4] vhost-user: Fix
./configure confusion". We agreed to drop it for now because it breaks
Linux ./configure --disable-system --disable-tools.

This patch series is fine as it is.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-11-12 10:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 17:11 [PATCH 0/3] vhost-user: ./configure improvements for 5.2 Stefan Hajnoczi
2020-11-10 17:11 ` [PATCH 1/3] meson: move vhost_user_blk_server to meson.build Stefan Hajnoczi
2020-11-11  9:41   ` Philippe Mathieu-Daudé
2020-11-11 11:44     ` Philippe Mathieu-Daudé
2020-11-11 11:54       ` Philippe Mathieu-Daudé
2020-11-12 10:58         ` Stefan Hajnoczi [this message]
2020-11-10 17:11 ` [PATCH 2/3] vhost-user-blk-server: depend on CONFIG_VHOST_USER Stefan Hajnoczi
2020-11-11  9:25   ` Philippe Mathieu-Daudé
2020-11-11 14:16     ` Stefan Hajnoczi
2020-11-10 17:11 ` [PATCH 3/3] configure: mark vhost-user Linux-only Stefan Hajnoczi
2020-11-10 17:44   ` Thomas Huth
2020-11-11  9:23   ` Philippe Mathieu-Daudé

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=20201112105807.GA1445788@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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).