[issue22625] When cross-compiling, don’t try to execute binaries

Martin Panter added the comment: In Issue 22359, Xavier has posted a patch that looks like a reasonable solution to both cross compiling and allowing parallel make. -- resolution: -> duplicate status: open -> closed superseder: -> Remove incorrect uses of recursive make _

[issue22625] When cross-compiling, don’t try to execute binaries

Alex Willmer added the comment: On 14 March 2016 at 01:05, Robert Collins wrote: > There are three platforms in play: target, host, build. > > Host is the platform where what you build should run on. > build is the platform we are building on. > target is the platform where the *output* of the b

[issue22625] When cross-compiling, don’t try to execute binaries

Martin Panter added the comment: Thanks Robert. Russell also pointed out on python-dev that the patches at Issue 23670 show how he is doing cross compilation, via a new high-level iOS/Makefile file. Here is a cut-down version of the parts that I find relevant: # Build for the native build host

[issue22625] When cross-compiling, don’t try to execute binaries

Robert Collins added the comment: So in general: https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/System-Type.html#System-Type and https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Hosts-and-Cross_002dCompilation.html There are three platforms in play:

[issue22625] When cross-compiling, don’t try to execute binaries

Martin Panter added the comment: In I suggested adding some makefile settings to manually override the pgen and _frozen_importlib programs. I imagine the changes would look something like cross-override.patch. Can someone wh

[issue22625] When cross-compiling, don’t try to execute binaries

Changes by Alex Willmer : -- nosy: +Alex.Willmer ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue22625] When cross-compiling, don’t try to execute binaries

ƦOB COASTN added the comment: Similar patch used for 3.5 Additionally required: -Python/importlib_external.h: $(srcdir)/Lib/importlib/_bootstrap_external.py Programs/_freeze_importlib +Python/importlib_external.h: $(srcdir)/Lib/importlib/_bootstrap_external.py + $(MAKE) Programs/_freeze_im

[issue22625] When cross-compiling, don’t try to execute binaries

Changes by Robert Collins : -- nosy: +rbcollins ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue22625] When cross-compiling, don’t try to execute binaries

Martin Panter added the comment: So is there somewhere that documents how cross compilation is meant to be done? I tried looking at , , and “./configure --help”, but found no hints for cro

[issue22625] When cross-compiling, don’t try to execute binaries

Changes by Ethan Furman : -- nosy: -ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue22625] When cross-compiling, don’t try to execute binaries

koobs added the comment: Incorrect recursive use of make will be fixed in default, 3.5, 3.4 (?), 2.7 in issue 22359, reflect the versions correctly here so they're not forgotten. -- nosy: +koobs versions: +Python 2.7, Python 3.4, Python 3.6 ___ Pytho

[issue22625] When cross-compiling, don’t try to execute binaries

Changes by Ethan Furman : -- nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue22625] When cross-compiling, don’t try to execute binaries

Matthias Klose added the comment: there are two approaches here, one to check in generated files and try to avoid the rebuild, or completely fix the cross build. I think the patch for the parallel build just was a bit over-eager -- ___ Python tracke

[issue22625] When cross-compiling, don’t try to execute binaries

Russell Keith-Magee added the comment: I'm looking into this issue because of issue23670 (iOS support). Am I correct in assuming that the right fix here is to identify a $(CC_FOR_BUILD) analog for $(PYTHON_FOR_BUILD) that will identify the build host's CC, enabling a build-host native $(PGEN)

[issue22625] When cross-compiling, don’t try to execute binaries

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue22625] When cross-compiling, don’t try to execute binaries

Georg Brandl added the comment: Indeed, that is an issue :( -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue22625] When cross-compiling, don’t try to execute binaries

Antoine Pitrou added the comment: This was removed in c2a53aa27cad, to fix #22359. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue22625] When cross-compiling, don’t try to execute binaries

Link Mauve added the comment: Thanks, this patch worked fine. :) I used to build pgen natively first, then make distclean and rebuild until it failed, and then put the native version back here, but this works much better! -- ___ Python tracker

[issue22625] When cross-compiling, don’t try to execute binaries

Georg Brandl added the comment: You're right, this can be avoided (although you will also have to patch the extension module build, which uses the just-built python executable). This problem occurs twice in the build process, once for pgen and once for _freeze_importlib. The problem is that t

[issue22625] When cross-compiling, don’t try to execute binaries

New submission from Link Mauve: ``` % make ./Programs/_freeze_importlib \ ./Lib/importlib/_bootstrap.py Python/importlib.h ./Programs/_freeze_importlib: ./Programs/_freeze_importlib: cannot execute binary file Makefile:710: recipe for target 'Python/importlib.h' failed make: *** [Python/