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 thomas-petazzoni
Recipients thomas-petazzoni
Date 2014-01-09.23:03:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389308587.95.0.49928374838.issue20212@psf.upfronthosting.co.za>
In-reply-to
Content
The build_ext logic uses sys.executable.startswith(os.path.join(sys.exec_prefix, "bin")) to determine whether we're building a third-party Python extension, or a built-in Python extension. However, this check is wrong in cross-compilation mode, because the host Python interpreter might very well be installed in its prefix, when it is used to cross-compile the target modules and extensions. The current check would mis-detect this as we're building third-party Python modules, while we are in fact building the internal Python modules of the target Python.

Therefore, use the existing sysconfig.python_build variable, which provides the information of whether we're building Python itself or not in a correct way.
History
Date User Action Args
2014-01-09 23:03:07thomas-petazzonisetrecipients: + thomas-petazzoni
2014-01-09 23:03:07thomas-petazzonisetmessageid: <1389308587.95.0.49928374838.issue20212@psf.upfronthosting.co.za>
2014-01-09 23:03:07thomas-petazzonilinkissue20212 messages
2014-01-09 23:03:07thomas-petazzonicreate