Fix locating Python interpreter when it isn't "python" (mono/mono#18197)
authorCalvin Buckley <calvin@cmpct.info>
Mon, 16 Dec 2019 10:06:00 +0000 (06:06 -0400)
committermonojenkins <jo.shields+jenkins@xamarin.com>
Mon, 16 Dec 2019 10:06:00 +0000 (11:06 +0100)
commit56141c36578590d0b82ca0a9b65c1ee9efe31bbd
tree465cc9b2e46de922b3b23b4c99586755e7771f3b
parent91d5b44577fe567bb0988df635b62df9c3fc6117
Fix locating Python interpreter when it isn't "python" (mono/mono#18197)

Fix locating Python interpreter when it isn't "python"

The "python" interpreter is specified by PEP-394. In it, an OS
can decide not to ship a "python" executable, and instead only
ship python2/3, providing some ambiguity for scripts that are
version-neutral, like the one Mono uses.

This uses an automake macro to locate a suitable Python, and
changes the makefile to use the located Python, whatever it may be.

Commit migrated from https://github.com/mono/mono/commit/84221f04b5ff1f5f6de69100494ae7cb3ba94975
src/mono/configure.ac
src/mono/mono/mini/Makefile.am.in