From: Paolo Bonzini <pbonzini@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"John Snow" <jsnow@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Rene Engel" <ReneEngel80@emailn.de>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Howard Spoelstra" <hsp.cat7@gmail.com>
Subject: Re: [NOTFORMERGE PATCH 1/2] configure: Use distrib meson
Date: Thu, 9 Nov 2023 00:33:20 +0100 [thread overview]
Message-ID: <CABgObfa00En_Hodn8UaAUNH5Eq1tMbBSAq+6j69pKaZ-iG3Xew@mail.gmail.com> (raw)
In-Reply-To: <44d8c245-122a-47f0-25e2-eae1dac8ac18@eik.bme.hu>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Il mer 8 nov 2023, 20:52 BALATON Zoltan <balaton@eik.bme.hu> ha scritto:
> AFAIU the problem is that macOS has system python in
> /Library/Frameworks/python.framework (or something like that) but homebrew
> does not use that but installs its own python somewhere in /opt and meson
> from homebrew uses that python but configure finds the system python which
> does not have meson so it then downloads its own meson but that's too old
> for macOS Sonoma
Correct (except s/downloads/installs/), basically --python/$PYTHON is the
sole interpreter used to run *any* Python code during the QEMU build. The
difference is that QEMU 8.1 would indeed download Meson, while QEMU 8.2
always uses the wheel that is shipped with QEMU. This change was done
because the embedded Meson is intended to be a "known good" version that we
(and pythondeps.toml) can point users to, in case a newer version from the
distro has issues. Of course the other side of the coin is that an older
version might not support new OSes as in this case.
The workaround below is not just a workaround but the intended solution if
one wants to use the Meson and Sphinx packages from homebrew, and cannot
modify the PATH to privilege homebrew's Python interpreter. In order to
support Sonoma out of the box with the system Python, however, we can bump
the shipped version of Meson to 1.2.x (and adjust pythondeps.toml).
Paolo
It should probably check for homebrew or macports
> locations too or check for meson and get the python that's using. A
> workaround apparently is to pass --python with the right path to
> configure.
>
[-- Attachment #2: Type: text/html, Size: 2277 bytes --]
next prev parent reply other threads:[~2023-11-08 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 18:32 [RFC PATCH 0/2] buildsys: Use host meson on macOS Sonoma (14) Philippe Mathieu-Daudé
2023-11-08 18:32 ` [NOTFORMERGE PATCH 1/2] configure: Use distrib meson Philippe Mathieu-Daudé
2023-11-08 19:01 ` Peter Maydell
2023-11-08 19:52 ` BALATON Zoltan
2023-11-08 23:33 ` Paolo Bonzini [this message]
2023-11-08 18:32 ` [PATCH 2/2] .gitlab-ci.d/cirrus: Add manual testing of macOS 14 (Sonoma) Philippe Mathieu-Daudé
2023-11-08 23:37 ` 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=CABgObfa00En_Hodn8UaAUNH5Eq1tMbBSAq+6j69pKaZ-iG3Xew@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=ReneEngel80@emailn.de \
--cc=alex.bennee@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=hsp.cat7@gmail.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).