On Fri, 5 Sept 2025 at 08:26, Paolo Bonzini wrote:
>
> On 9/4/25 17:11, Peter Foley wrote:
> > Relying on `python3` to be avilable in $PATH doesn't work in some build
> > environments. Update the build files to use the found python binary
> > explicitly.
>
> Meson already does this, if the file is
On Fri, Sep 5, 2025 at 5:01 PM Peter Foley wrote:
> Interesting, that's not what I'm seeing in practice.
> For example, locally reverting the change to block/meson.build results in:
> FAILED: block/module_block.h
> /build/work/046b6fd7014012220d3de53b1bd62f6eb1e9/google3/third_party/qemu/block/../
On Fri, Sep 5, 2025 at 3:25 AM Paolo Bonzini wrote:
> On 9/4/25 17:11, Peter Foley wrote:
> > Relying on `python3` to be avilable in $PATH doesn't work in some build
> > environments. Update the build files to use the found python binary
> > explicitly.
>
> Meson already does this, if the file is
On 9/4/25 17:11, Peter Foley wrote:
Relying on `python3` to be avilable in $PATH doesn't work in some build
environments. Update the build files to use the found python binary
explicitly.
Meson already does this, if the file is not executable. See
docs/devel/build-system.rst:
Meson has a
Relying on `python3` to be avilable in $PATH doesn't work in some build
environments. Update the build files to use the found python binary
explicitly.
Signed-off-by: Peter Foley
---
block/meson.build | 6 ++
meson.build | 10 +-
plugins/meson.build | 2 +-
3 files change
