[issue22724] byte-compile fails for cross-builds

Xavier de Gaye added the comment: PYTHON_FOR_BUILD does not use PYTHONPATH in the implementation of (closed) PR 17420 and should fix the current issue as a side effect. FWIW, PR 17420 fixes cross-compilation of third-party extension modules by replacing the complex PYTHON_FOR_BUILD command

[issue22724] byte-compile fails for cross-builds

Andrew Aladjev added the comment: I've made a quick test of all patches provided. All patches have failed to fix it. The problem is more heavy than it looks like. Please look at the following code: PYTHON_FOR_BUILD='_PYTHON_PROJECT_BASE=$(abs_builddir)

[issue22724] byte-compile fails for cross-builds

Andrew Aladjev added the comment: Hello. I've provided a double recompilation workaround in the following gentoo bug https://bugs.gentoo.org/705970. You can use it for now if you don't want to wait until this issue will be fixed. I will try patches provided by people in this issue today's

[issue22724] byte-compile fails for cross-builds

Change by Andrew Aladjev : -- nosy: +puchenyaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22724] byte-compile fails for cross-builds

Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22724] byte-compile fails for cross-builds

Xavier de Gaye added the comment: Cross-compilation of Android x86_64 on a linux x86_64 host followed by 'make install' does not fail anymore after the changes made in issue 27917. As expected since the triplets are different now when the target is an Android platform. --

[issue22724] byte-compile fails for cross-builds

Xavier de Gaye added the comment: Patch rebased to current tip. To summarize: * The root cause of the problem reported by Benedikt still exists. * The problem is hidden now that the shared libraries names include the PLATFORM_TRIPLET. * But byte-compilation still fails for cross-builds when

[issue22724] byte-compile fails for cross-builds

Changes by Xavier de Gaye : -- nosy: +thomas-petazzoni ___ Python tracker ___ ___

[issue22724] byte-compile fails for cross-builds

Xavier de Gaye added the comment: 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

[issue22724] byte-compile fails for cross-builds

Xavier de Gaye added the comment: > On Android cross-builds, it should be possible to reproduce the failure when > the build system and the host system have the same PLATFORM_TRIPLET I confirm that this is the case. The following backtrace is produced when cross-building and installing

[issue22724] byte-compile fails for cross-builds

Xavier de Gaye added the comment: The byte-compiling for cross-builds fails because PYTHON_FOR_BUILD defined in configure, sets PYTHONPATH with the directory of the newly built extension modules shared libraries and because PYTHON_FOR_BUILD is used to run compileall.py in the Makefile.

[issue22724] byte-compile fails for cross-builds

Nick Coghlan added the comment: Issue 23968 moves _sysconfigdata.py to an arch dependendent directory -- dependencies: +rename the platform directory from plat-$(MACHDEP) to plat-$(PLATFORM_TRIPLET) nosy: +ncoghlan ___ Python tracker

[issue22724] byte-compile fails for cross-builds

Changes by Roumen Petrov bugtr...@roumenpetrov.info: -- nosy: +rpetrov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22724 ___ ___

[issue22724] byte-compile fails for cross-builds

Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: +doko ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22724 ___ ___ Python-bugs-list

[issue22724] byte-compile fails for cross-builds

Changes by Benedikt Morbach benedikt.morb...@googlemail.com: -- versions: +Python 3.5, Python 3.6 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22724 ___

[issue22724] byte-compile fails for cross-builds

New submission from Benedikt Morbach: For cross-builds the byte-compiling and 2to3 Grammar generation fail. This is because PYTHONPATH/sys.path includes 'build/lib.$PLATFORM', in which the compiled .so modules reside. The host python obviously barfs on those, as they are compiled for a

[issue22724] byte-compile fails for cross-builds

Benedikt Morbach added the comment: alternatively, introduce a $(PYTHON_FOR_INSTALL), which doesn't set PYTHONPATH. Then run those steps using that, with the Makefile setting PYTHONPATH=$(DESTDIR)$(LIBDEST), which doesn't contain the compiled modules at that point. The first solution looks