➜

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 martin.panter
Recipients EdSchouten, martin.panter
Date 2016-09-10.23:21:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473549661.73.0.313124694885.issue28066@psf.upfronthosting.co.za>
In-reply-to
Content 
Can you get your importlib changes so they are compatible with a native build? If so, maybe you can build the frozen module with a native build rather than a cross build.

“freeze_importlib is built using the compiler for the target”: I may be mistaken, but I thought we recently prevented this from being cross-compiled: Issue 27641, revision bc677cb34889, Jul 2016. Your patch seems to be based ontop of this change. Perhaps you have found some way to bypass that cross-compilation detection logic.

The addition of $(FREEZE_IMPORTLIB) is a bit like the outdated cross-override.patch I once proposed for Issue 22625.
History
Date User Action Args
2016-09-10 23:21:01martin.pantersetrecipients: + martin.panter, EdSchouten
2016-09-10 23:21:01martin.pantersetmessageid: <1473549661.73.0.313124694885.issue28066@psf.upfronthosting.co.za>
2016-09-10 23:21:01martin.panterlinkissue28066 messages
2016-09-10 23:21:01martin.pantercreate