From: Olaf Hering <olaf@aepfle.de>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Greg Kurz <groug@kaod.org>
Subject: Re: virtfs-proxy-helper fails due to bogus libattr test
Date: Tue, 12 Jan 2021 15:44:43 +0100 [thread overview]
Message-ID: <20210112154443.564deecc.olaf@aepfle.de> (raw)
In-Reply-To: <2315616.PpvBb8DKss@silver>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Am Tue, 12 Jan 2021 13:26:00 +0100
schrieb Christian Schoenebeck <qemu_oss@crudebyte.com>:
> Olaf, could you run a 'git bisect' to identify the relevant commit causing this?
attr was recently moved from configure to meson.
After further inspection it turned out that messages on stderr may have no meaning for meson.
Elsewhere in the log I see:
libcap-ng support: YES
ATTR/XATTR support: YES
VirtFS support: YES
There is also --enable-tools, so CONFIG_TOOLS should be true.
have_virtfs_proxy_helper might be false, at least there is no indication that a build of /usr/lib/virtfs-proxy-helper was attempted.
However, where is CONFIG_VIRTFS supposed to come from? It seems have_system influences "have_virtfs". There is apparently no easy way to see if 'have_system' became true.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-12 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 9:51 virtfs-proxy-helper fails due to bogus libattr test Olaf Hering
2021-01-12 12:26 ` Christian Schoenebeck via
2021-01-12 12:29 ` Daniel P. Berrangé
2021-01-12 13:08 ` Paolo Bonzini
2021-01-12 14:47 ` Olaf Hering
2021-01-12 15:03 ` Paolo Bonzini
2021-01-12 14:44 ` Olaf Hering [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=20210112154443.564deecc.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=groug@kaod.org \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.