From: Thomas Huth <thuth@redhat.com>
To: Cole Robinson <crobinso@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, alex.bennee@linaro.org
Subject: Re: configure --without-default-features confusion
Date: Tue, 13 Jul 2021 09:20:37 +0200 [thread overview]
Message-ID: <3261e019-9240-0fe2-0872-e5a77100957e@redhat.com> (raw)
In-Reply-To: <d7cb1c8f-036d-1be8-e259-cd71ce8a1649@redhat.com>
On 08/07/2021 21.12, Cole Robinson wrote:
> Hi all,
>
> I'm a bit confused about the intended scope of ./configure
> --without-default-features. When I try it here there's still lots of
> stuff enabled:
>
> $ ./configure --without-default-features
> ...
> VNC support : YES
> VNC SASL support : YES
> VNC JPEG support : YES
> VNC PNG support : YES
> brlapi support : YES
> vde support : NO
> netmap support : NO
> Linux AIO support : NO
> Linux io_uring support : YES
> ATTR/XATTR support : YES
> RDMA support : NO
> PVRDMA support : NO
> ...
>
> So rdma/pvrdma, which I have libs for, are disabled, but brlapi, which I
> have libs for, is auto enabled. VNC is not dependent on any external
> libraries, but it's still enabled. Etc.
>
> ...okay now that I poke at this a bit, the brlapi bit and most (but not
> all) other features are disabled if I fix this:
>
>> diff --git a/configure b/configure
>> index 650d9c0735..a71ebe10ff 100755
>> --- a/configure
>> +++ b/configure
>> @@ -5189,7 +5189,7 @@ if test "$skip_meson" = no; then
>> -Ddocs=$docs -Dsphinx_build=$sphinx_build -Dinstall_blobs=$blobs \
>> -Dvhost_user_blk_server=$vhost_user_blk_server -Dmultiprocess=$multiprocess \
>> -Dfuse=$fuse -Dfuse_lseek=$fuse_lseek -Dguest_agent_msi=$guest_agent_msi -Dbpf=$bpf\
>> - $(if test "$default_features" = no; then echo "-Dauto_features=disabled"; fi) \
>> + $(if test "$default_feature" = no; then echo "-Dauto_features=disabled"; fi) \
Looks like you've found a bug... Could you please send this as a proper
patch to the mailing list?
> But there's still a handful of things that are left enabled, for example
> VNC, xen, vhost-vdpa, ...
>
> Is the intention for this knob to be a 'disable everything'?
I guess yes, but I think it's still work in progress ... not every feature
has been revisited since this switch has been introduced.
Thomas
next prev parent reply other threads:[~2021-07-13 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 19:12 configure --without-default-features confusion Cole Robinson
2021-07-13 7:20 ` Thomas Huth [this message]
2021-07-13 9:00 ` 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=3261e019-9240-0fe2-0872-e5a77100957e@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crobinso@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).