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 christian.heimes
Recipients Alex.Willmer, christian.heimes, ethan smith
Date 2021-11-27.19:03:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638039821.46.0.168368220549.issue45909@roundup.psfhosted.org>
In-reply-to
Content
I just realized that PYTHON_FOR_BUILD is far more complicated. Our WASM build system sets the env var to "$(pwd)/cpython/builddir/build/python". The configure script expects us to set several additional env vars.

The logic goes like this for cross compiling:

if PYTHON_FOR_BUILD is empty:
    find Python interpreter with same version as PACKAGE_VERSION
    set PYTHON_FOR_BUILD='_PYTHON_PROJECT_BASE=$(abs_builddir) _PYTHON_HOST_PLATFORM=$(_PYTHON_HOST_PLATFORM) PYTHONPATH=$(shell test -f pybuilddir.txt && echo $(abs_builddir)/`cat pybuilddir.txt`:)$(srcdir)/Lib _PYTHON_SYSCONFIGDATA_NAME=_sysconfigdata_$(ABIFLAGS)_$(MACHDEP)_$(MULTIARCH) '$interp
else:
    use user-supplied PYTHON_FOR_BUILD

Since we don't set any of the variables _PYTHON_PROJECT_BASE, _PYTHON_HOST_PLATFORM, and _PYTHON_SYSCONFIGDATA_NAME, we get wrong sysconfig data file.
History
Date User Action Args
2021-11-27 19:03:41christian.heimessetrecipients: + christian.heimes, Alex.Willmer, ethan smith
2021-11-27 19:03:41christian.heimessetmessageid: <1638039821.46.0.168368220549.issue45909@roundup.psfhosted.org>
2021-11-27 19:03:41christian.heimeslinkissue45909 messages
2021-11-27 19:03:41christian.heimescreate