On 07/03/19 14:09, Peter Maydell wrote:
> On Thu, 7 Mar 2019 at 12:56, Paolo Bonzini <pbonz...@redhat.com> wrote:
>> In any case, this wouldn't change; as you suggest below, configure could
>> remain as a front-end (well, in-srcdir builds are not supported by
>> Meson, so "../configure && ninja" perhaps).
>
> As an aside, it might be a nice idea to drop the in-srcdir
> build altogether for QEMU anyway -- it's not really a very
> good idea and it means our build system has to cope with two
> different ways of working to no particularly useful end.
I was actually going to propose that, but I was afraid of throwing two
bombs in the same day. :)
> Of the various hosts I do builds on:
> * OSX is 2.7 only
> * the ppc64 box in the gcc compile farm is 2.7 and 3.4
> ("Centos 7.5.1804")
> * the aarch64 box in the gcc compile farm is 2.7 and 3.4
> ("Ubuntu 14.04.5 LTS", aka trusty)
OS X will need to get Python 3 from Homebrew sooner or later anyway.
Trusty does have a python3.5 package, perhaps you could ask the
maintainers to install it.
CentOS 7 doesn't have "native" Python 3 (even the 3.4 version you have
there is probably coming from Fedora) but it has software collections,
where you have to do "scl enable rh-python35 './configure && make'".
You can check if scl and the rh-python35 software collections are
already installed.
Paolo
