The array module is the current culprit.
Are there details about the freeze process at Python.org? That may help me
figure out what and why my build breaks?
I'll try my best to get a traceback...I don't have a working gdb in this env
yet...and if I do get one I'll add it to the email I send to python-sig
On February 3, 2015 12:10:54 AM CST, Eric Snow <ericsnowcurren...@gmail.com>
wrote:
>On Mon, Feb 2, 2015 at 12:36 PM, Cyd Haselton <chasel...@gmail.com>
>wrote:
>> After fixing a segfault issue (many thanks Ryan) I'm back to the same
>issue
>> I was having with Python 2.7.8; the newly built python throws an
>undefined
>> reference to dlopen when running setup.py...specifically when
>importing
>> just-built extensions
>>
>> I've managed to narrow the problem down to the following line:
>>
>> importlib._bootstrap._SpecMethods(spec).load()
>
>That call is where modules are created (and executed) via the loader
>designated for the module by the import machinery. So a problem here
>may simply reflect a problem with the loader. Which module is being
>imported when you run into trouble? Is it a C-extension module?
>
>Also keep in mind that basically everything in importlib._bootstrap is
>frozen into your Python binary when you build Python (or should be).
>So if you are seeing any errors related to something missing or broken
>in importlib._bootstrap, it could be related to the build step where
>importlib gets frozen.
>
>Either way, more info (e.g. a traceback) would be great if you need
>more help.
>
>-eric
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
