From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Hartmayer <mhartmay@linux.ibm.com>, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH] meson: vhost-user-gpu/virtiofsd: use absolute path
Date: Tue, 3 Nov 2020 12:55:25 +0100 [thread overview]
Message-ID: <4798e23a-da0b-22f6-05bd-2373768a241c@redhat.com> (raw)
In-Reply-To: <877dr28ysh.fsf@linux.ibm.com>
On 03/11/20 12:28, Marc Hartmayer wrote:
> On Tue, Nov 03, 2020 at 12:23 PM +0100, Marc Hartmayer <mhartmay@linux.ibm.com> wrote:
>> The option `libexecdir` is relative to `prefix` (see
>> https://mesonbuild.com/Builtin-options.html), so we have to be aware
>> of this when creating 50-qemu-gpu.json and
>> 50-qemu-virtiofsd.json. Otherwise, tools like libvirt will not be able
>> to find the executable.
>>
>> Fixes: 16bf7a3326d8 ("configure: move directory options from config-host.mak to meson")
>> Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
>> ---
>> contrib/vhost-user-gpu/meson.build | 2 +-
>> tools/virtiofsd/meson.build | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/contrib/vhost-user-gpu/meson.build b/contrib/vhost-user-gpu/meson.build
>> index 37ecca13cafb..c487ca72c1ff 100644
>> --- a/contrib/vhost-user-gpu/meson.build
>> +++ b/contrib/vhost-user-gpu/meson.build
>> @@ -9,6 +9,6 @@ if 'CONFIG_TOOLS' in config_host and 'CONFIG_VIRGL' in config_host \
>>
>> configure_file(input: '50-qemu-gpu.json.in',
>> output: '50-qemu-gpu.json',
>> - configuration: { 'libexecdir' : get_option('libexecdir') },
>> + configuration: { 'libexecdir' : get_option('prefix') / get_option('libexecdir') },
>> install_dir: qemu_datadir / 'vhost-user')
>> endif
>> diff --git a/tools/virtiofsd/meson.build b/tools/virtiofsd/meson.build
>> index e1a4dc98d9ec..17edecf55c0a 100644
>> --- a/tools/virtiofsd/meson.build
>> +++ b/tools/virtiofsd/meson.build
>> @@ -15,5 +15,5 @@ executable('virtiofsd', files(
>>
>> configure_file(input: '50-qemu-virtiofsd.json.in',
>> output: '50-qemu-virtiofsd.json',
>> - configuration: { 'libexecdir' : get_option('libexecdir') },
>> + configuration: { 'libexecdir' : get_option('prefix') / get_option('libexecdir') },
>> install_dir: qemu_datadir / 'vhost-user')
>> --
>> 2.25.4
>>
>>
>
> It’s probably not the best way to fix it, but at least a good hint
> what’s wrong :)
No, it's okay. I queued it.
Paolo
next prev parent reply other threads:[~2020-11-03 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 11:23 [PATCH] meson: vhost-user-gpu/virtiofsd: use absolute path Marc Hartmayer
2020-11-03 11:28 ` Marc Hartmayer
2020-11-03 11:55 ` Paolo Bonzini [this message]
2020-11-03 12:02 ` Marc Hartmayer
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=4798e23a-da0b-22f6-05bd-2373768a241c@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=mhartmay@linux.ibm.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).