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 xdegaye
Recipients ned.deily, rossburton, xdegaye
Date 2019-03-02.09:47:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551520063.83.0.788942939162.issue36125@roundup.psfhosted.org>
In-reply-to
Content
@Ross

> The intention appears to be that the sysconfig.py in the build is used.  In my case that directory is also full of shared libraries that Python happily loads, and then fails.

No, the intention is that the native python finds the sysconfigdata module named $_PYTHON_SYSCONFIGDATA_NAME that is located in the directory where the extensions modules (.so libraries) have been cross-compiled. $_PYTHON_SYSCONFIGDATA_NAME is a pure python module, so it can be loaded by the native python.

Please note that in your first post PYTHONPATH is missing the first part, i.e. the path to this directory obtained with:
    $(shell test -f pybuilddir.txt && echo $(abs_builddir)/`cat pybuilddir.txt`:)

When PYTHON_FOR_BUILD runs, it does not load any extension module so the Illegal instruction may be caused by some other problem.
History
Date User Action Args
2019-03-02 09:47:43xdegayesetrecipients: + xdegaye, ned.deily, rossburton
2019-03-02 09:47:43xdegayesetmessageid: <1551520063.83.0.788942939162.issue36125@roundup.psfhosted.org>
2019-03-02 09:47:43xdegayelinkissue36125 messages
2019-03-02 09:47:43xdegayecreate