On Fri, 21 May 2021 at 14:27, Paolo Bonzini <pbonz...@redhat.com> wrote: > > 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.
It's the gcc compile farm's ppc64 box, whose /etc/redhat-release says it's running "CentOS Linux release 7.9.2009 (AltArch)". I don't have control over system upgrades for it. I do notice that there's a newer ppc64 box in the farm running Debian 11 (bullseye), so maybe we could just switch to using that. > > 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. Mmm. I think I started using cflags for that back when configure never enabled Werror for anything except Linux. I'll check that there isn't some subtle issue with -Werror and -Wno-error=foo needing to be in a particular order in the command line, but otherwise I'll just update the configure rune for that build box. thanks -- PMM