On Thu, Jun 16, 2022 at 4:29 PM Xavier de Gaye <xdeg...@gmail.com> wrote: > A Google search on "andoid x86_64" gives about 10,900,000 results, showing > that cross-compiling is quite common for the case where the build system and > the host system have the same PLATFORM_TRIPLET as when building android > x86_64 on an x86_64. So the argument that this problem is not worth fixing > because no one has to cross-compile in this environment, IMHO this argument > is not valid.
You misunderstood me. I didn't say that the issue must not be fixed. I only tried to explain why it was not fixed yet. > Yes this issue does explain how to reproduce the problem. It even shows the > backtrace printed when attempting to cross-build Android x86_64 on a linux > x86_64. > To reproduce the issue, just cross-build python for android x86_64 following > the well documented process by the Android team. > It is not clear how this backtrace can be missed when reading the issue ! Is there a way to reproduce the issue without Android? Like building Python on x86-64 for musl on a system using glibc? > There is also a patch provided in this issue that is straightforward and that > does not involve any change on distutils, only the Makefile and configure. That's interesting, since distutils is scheduled from removal in Python 3.12. Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/B74YHEAKQZF2XZEOH6SKZRHXQGU4A5OD/ Code of Conduct: http://python.org/psf/codeofconduct/
