<div dir="ltr"><div dir="ltr">On Mon, 9 Sep 2019 at 18:49, Ross Burton <<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>> wrote:<br></div><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> As I had previously suggested... can you try adding 'python3' to DEPENDS <br>
> of mesa, and see if that helps please? I think that would allow avoiding <br>
> this patch altogether.<br>
<br>
So why does Meson need *target* Python to be present when building Mesa?<br></blockquote><div><br></div><div>Because mesa does this:</div><div><br></div><div>prog_python = import('python').find_installation('python3')</div><div><br></div><div>and find_installation() method of meson does not merely look for the native python binary, it runs the binary with a meson-supplied python script designed to obtain all sorts of information, including target-specific things that we patch native python to report. If the target python installation is not present in sysroot, the script will fail, and meson will declare that 'there is no valid installation of python on your system'.<br></div><div><br></div><div>Alex<br> </div></div></div>
</div>