New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_struct module compilation error under Cygwin 1.7.17 on Python 3.4 #65323
Comments
Dear all, I am compiling Python 3.4 on Cygwin 1.7.17. The following has been done in order to reach the point where _struct module failed.
The issue happened during make: Please feel free to find the build.log and the output of _struct.c.txt (gcc with -dD -E -DPy_BUILD_core) for more information. Thanks in advance, |
The full build log |
This looks like a duplicate of bpo-6672. |
I wrote a patch file. |
Yamamoto, Thanks, the patch you offered did make the _struct error disappeared. I will do a bit more testing. Dellair |
Hello masamoto, The patch you provided works quite well. Thanks, |
I have solved about compiling _struct module too. |
Fixed with the patch. |
New changeset 3bde312ae936 by Zachary Ware in branch 'default': |
For future reference, having a patch attached to the issue does not mean the issue is fixed, and it should not be closed. |
PyType_Ready() should be called for unpackiter_type. See also bpo-26906. |
I wrote a patch to add the unpackiter_type initialization into PyInit__struct function. I has confirmed solve bpo-28337 on ubuntu x86 16.04. |
Do we not have a unit test for that? |
unpack_iterator type has not been registered into _struct module. And all users get only unpack_iterator object from function returning iterator. The object iterating doesn't need reference to type. Therefore, I think issue finish by PyType_Ready fix because this segfault doesn't have big impact. However, I think if possible, it is preferable that extension module having un-initialize type objects gets a compile error at build time. And impossible case for compile error is better that wrong extension module always fails import. |
New changeset c4eb211fb38b by Zachary Ware in branch 'default': |
Thanks for the patch again :). The last idea you mentioned sounds somewhat interesting, please open a new issue for it if you'd like to pursue it. |
Misc/NEWS
so that it is managed by towncrier #552Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: