This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients Benedikt.Morbach, doko, ncoghlan, rpetrov, xdegaye
Date 2016-07-01.15:15:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467386121.25.0.984969238428.issue22724@psf.upfronthosting.co.za>
In-reply-to
Content
Adding -E to PYTHON_FOR_BUILD fixes the x86_64 install because in my Android cross-build setup, the native interpreter is built from the same source tree as the cross-build. However, currently the interpreter used for the cross-build may be any interpreter found in PATH and can import an incorrect importlib.util.MAGIC_NUMBER if PYTHONPATH is not set properly. So this new patch does not use -E and splits PYTHON_FOR_BUILD into two variables, PY_BUILD_ENVIRON that sets the environment variables and PYTHON_FOR_BUILD, the interpreter. PY_BUILD_ENVIRON is not used when running compileall.

Tested by running the test suite on the Android i686 and x86_64 emulators (excluding test_ctypes that segfaults python on x86_64). The tests cannot be run with a cross-build where PYTHON_FOR_BUILD is python 3.5.1 because of issue 27434.
History
Date User Action Args
2016-07-01 15:15:21xdegayesetrecipients: + xdegaye, doko, ncoghlan, rpetrov, Benedikt.Morbach
2016-07-01 15:15:21xdegayesetmessageid: <1467386121.25.0.984969238428.issue22724@psf.upfronthosting.co.za>
2016-07-01 15:15:21xdegayelinkissue22724 messages
2016-07-01 15:15:21xdegayecreate