From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 00/26] Misc patches for 2021-05-20
Date: Fri, 21 May 2021 15:27:16 +0200 [thread overview]
Message-ID: <7775729e-e217-f469-429b-a966996a1ef3@redhat.com> (raw)
In-Reply-To: <CAFEAcA_MV=UiHW4Kp3Zb4iT_5BHgqVwj9Qem1xjmp1AJ++K=sQ@mail.gmail.com>
On 20/05/21 15:26, Peter Maydell wrote:
> WARNING: Project specifies a minimum meson_version '>=0.55.0' but uses
> features which were added in newer versions:
> * 0.57.0: {'test() timeout <= 0'}
>
> ERROR: Could not detect Ninja v1.8.2 or newer
>
> (This system has ninja-build 1.7.2.)
What OS is it, and is there any chance of updating it? ninja 1.7 was
released in 2017, and I checked that all the supported OSes for QEMU
have 1.8 before sending the pull request.
> Also, my OSX build which I configure with
> ../..configure --extra-cflags='-fdiagnostics-color=never -Werror
> -Wno-error=deprecated-declarations'
>
> now triggers a meson.build warning:
>
> ../../meson.build:118: WARNING: Consider using the built-in werror
> option instead of using "-Werror".
> ../../meson.build:120: WARNING: Consider using the built-in werror
> option instead of using "-Werror".
> ../../meson.build:122: WARNING: Consider using the built-in werror
> option instead of using "-Werror".
Which makes sense since we have --enable/--disable-werror.
> Also also, dropping the merge commit reveals that the pullreq somehow
> broke the build trees such that trying to do a build on master no
> longer works: [...] This seems like a meson bug
It is and has been fixed since in Meson, but the older version obviously
doesn't have the fix.
Paolo
next prev parent reply other threads:[~2021-05-21 13:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 8:22 [PULL 00/26] Misc patches for 2021-05-20 Paolo Bonzini
2021-05-20 8:22 ` [PULL 01/26] configure: Only clone softfloat-3 repositories if TCG is enabled Paolo Bonzini
2021-05-20 8:22 ` [PULL 02/26] configure: check for submodules if --with-git-submodules=ignore Paolo Bonzini
2021-05-20 8:22 ` [PULL 03/26] configure: simplify assignment to GIT_SUBMODULES Paolo Bonzini
2021-05-20 8:22 ` [PULL 04/26] hw/mem/nvdimm: Use Kconfig 'imply' instead of 'depends on' Paolo Bonzini
2021-05-20 8:22 ` [PULL 05/26] i386/cpu: Expose AVX_VNNI instruction to guest Paolo Bonzini
2021-05-20 8:22 ` [PULL 06/26] meson: bump submodule to 0.57.2 Paolo Bonzini
2021-05-20 8:22 ` [PULL 07/26] object: add more commands to preconfig mode Paolo Bonzini
2021-05-20 8:22 ` [PULL 08/26] qtest: add a QOM object for qtest Paolo Bonzini
2021-05-20 8:22 ` [PULL 09/26] KVM: do not allow setting properties at runtime Paolo Bonzini
2021-05-20 8:22 ` [PULL 10/26] memory: Introduce log_sync_global() to memory listener Paolo Bonzini
2021-05-20 8:22 ` [PULL 11/26] KVM: Use a big lock to replace per-kml slots_lock Paolo Bonzini
2021-05-20 8:22 ` [PULL 12/26] KVM: Create the KVMSlot dirty bitmap on flag changes Paolo Bonzini
2021-05-20 8:22 ` [PULL 13/26] KVM: Provide helper to get kvm dirty log Paolo Bonzini
2021-05-20 8:22 ` [PULL 14/26] KVM: Provide helper to sync dirty bitmap from slot to ramblock Paolo Bonzini
2021-05-20 8:22 ` [PULL 15/26] KVM: Simplify dirty log sync in kvm_set_phys_mem Paolo Bonzini
2021-05-20 8:22 ` [PULL 16/26] KVM: Cache kvm slot dirty bitmap size Paolo Bonzini
2021-05-20 8:22 ` [PULL 17/26] KVM: Add dirty-ring-size property Paolo Bonzini
2021-05-20 8:22 ` [PULL 18/26] KVM: Disable manual dirty log when dirty ring enabled Paolo Bonzini
2021-05-20 8:22 ` [PULL 19/26] KVM: Dirty ring support Paolo Bonzini
2021-05-20 8:22 ` [PULL 20/26] tests/qtest/fuzz: Fix build failure Paolo Bonzini
2021-05-20 8:22 ` [PULL 21/26] meson: Set implicit_include_directories to false Paolo Bonzini
2021-05-20 8:22 ` [PULL 22/26] remove qemu-options* from root directory Paolo Bonzini
2021-05-20 8:22 ` [PULL 23/26] replication: move include out of " Paolo Bonzini
2021-05-20 8:22 ` [PULL 24/26] vl: allow not specifying size in -m when using -M memory-backend Paolo Bonzini
2021-05-20 8:22 ` [PULL 25/26] qemu-config: load modules when instantiating option groups Paolo Bonzini
2021-05-20 8:22 ` [PULL 26/26] scsi-generic: pass max_segments via max_iov field in BlockLimits Paolo Bonzini
2021-05-20 8:54 ` [PULL 00/26] Misc patches for 2021-05-20 no-reply
2021-05-20 13:26 ` Peter Maydell
2021-05-20 14:20 ` Peter Maydell
2021-05-20 14:25 ` Peter Maydell
2021-05-21 13:27 ` Paolo Bonzini [this message]
2021-05-21 13:44 ` Peter Maydell
2021-05-24 9:42 ` Paolo Bonzini
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=7775729e-e217-f469-429b-a966996a1ef3@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).