Ned Deily added the comment: This appears to be another variation on the problem recently identified in Issue21166, namely that the pybuildir.txt Makefile rule can incorrectly import a shared library module from a previously installed Python instance and, if the ABIs of the installed and being-built Pythons differ, the newly-built interpreter can fail in various ways. From your supplied trace, one can see that _heapq.so has incorrectly been inported from the installed system Python 3.4 which was probably built with --without-pymalloc:
#7 0x00007ff2f9ee2a6d in PyInit__heapq () from /usr/lib/python3.4/lib-dynload/64/_heapq.so #8 0x00007ff2f94c7c78 in _PyImport_LoadDynamicModule () from /builds/jbeck/ul-python-3/components/python/python34/build/amd64/libpython3.4m.so.1.0 The fixes for Issue21166, when applied, should prevent this problem. ---------- components: +Build -Interpreter Core nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Bus error in pybuilddir.txt 'python -m sysconfigure --generate-posix-vars' build step _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21412> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
