From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v3 00/22] Build system + misc changes for 2020-10-16
Date: Sat, 31 Oct 2020 15:46:41 +0000 [thread overview]
Message-ID: <CAFEAcA8CEDe6yinvaTMqbho7i_ZBWOSYG8_J_R5Xx56VxXD=uQ@mail.gmail.com> (raw)
In-Reply-To: <20201017144805.1641371-1-pbonzini@redhat.com>
On Sat, 17 Oct 2020 at 15:50, Paolo Bonzini <pbonzini@redhat.com> wrote:
> ----------------------------------------------------------------
> * Drop ninjatool and just require ninja (Paolo)
> * Fix docs build under msys2 (Yonggang)
> * HAX snafu fix (Claudio)
> * Disable signal handlers during fuzzing (Alex)
> * Miscellaneous fixes (Bruce, Greg)
>
> Yonggang Luo (3):
> docs: Fix Sphinx configuration for msys2/mingw
> meson: Move the detection logic for sphinx to meson
> cirrus: Enable doc build on msys2/mingw
I've just noticed that there seems to be a minor bug with
the new sphinx detection logic: if the Sphinx is the
wrong version then it prints:
Program sphinx-build found: YES
../../docs/meson.build:30: WARNING: exists but it is either too old
or uses too old a Python version
ie it hasn't actually managed to substitute in the
program name, so there's just a double-space after
WARNING: instead...
thanks
-- PMM
next prev parent reply other threads:[~2020-10-31 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 14:48 [PULL v3 00/22] Build system + misc changes for 2020-10-16 Paolo Bonzini
2020-10-17 14:48 ` [PULL 08/22] add ninja to dockerfiles, CI configurations and test VMs Paolo Bonzini
2020-10-17 14:48 ` [PULL 10/22] build: replace ninjatool with ninja Paolo Bonzini
2020-10-19 8:40 ` [PULL v3 00/22] Build system + misc changes for 2020-10-16 Peter Maydell
2020-10-31 15:46 ` Peter Maydell [this message]
2020-10-31 19:14 ` 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='CAFEAcA8CEDe6yinvaTMqbho7i_ZBWOSYG8_J_R5Xx56VxXD=uQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=pbonzini@redhat.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).