From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: some mason warnings during latest master build
Date: Mon, 31 Aug 2020 14:13:38 +0200 [thread overview]
Message-ID: <ac653cb5-516b-d3bf-aa63-5d4480b85dbb@redhat.com> (raw)
In-Reply-To: <ff4e5f09-fb36-8ab6-1c40-210193e2676b@suse.de>
On 31/08/20 13:46, Claudio Fontana wrote:
>
> Hello Paolo,
>
> just FYI I am getting a few WARNINGS on latest master with mason, not sure if you get them as well:
>
> ./configure --enable-tcg --disable-kvm --disable-hax
>
> [...]
>
> Found ninja-1.10.0 at /usr/bin/ninja
> WARNING: custom_target 'shared QAPI source files' has more than one output! Using the first one.
> WARNING: custom_target 'QGA QAPI files' has more than one output! Using the first one.
> WARNING: custom_target 'QAPI files for qemu-storage-daemon' has more than one output! Using the first one.
> WARNING: custom_target 'QAPI doc' has more than one output! Using the first one.
> WARNING: custom_target 'dbus-vmstate description' has more than one output! Using the first one.
> WARNING: custom_target 'tools man pages' has more than one output! Using the first one.
> WARNING: custom_target 'system man pages' has more than one output! Using the first one.
Yes, these are harmless and will go away with Meson 0.55.1 (from either
distro or submodule).
Paolo
> Command line for building ['libcommon.fa'] is long, using a response file
> Command line for building ['libqemu-aarch64-softmmu.fa'] is long, using a response file
> Command line for building ['qemu-system-aarch64'] is long, using a response file
prev parent reply other threads:[~2020-08-31 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 11:46 some mason warnings during latest master build Claudio Fontana
2020-08-31 12:13 ` Paolo Bonzini [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=ac653cb5-516b-d3bf-aa63-5d4480b85dbb@redhat.com \
--to=pbonzini@redhat.com \
--cc=cfontana@suse.de \
--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).