[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: virtfs-proxy-helper fails due to bogus libattr test
From: |
Olaf Hering |
Subject: |
Re: virtfs-proxy-helper fails due to bogus libattr test |
Date: |
Tue, 12 Jan 2021 15:44:43 +0100 |
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
pgpLxxztZALLu.pgp
Description: Digitale Signatur von OpenPGP