Skip to content
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

Python 2.7.2 don't build cleanly with GCC ≥ 4.8 #321

Closed
rdoursenaud opened this issue Feb 1, 2015 · 3 comments
Closed

Python 2.7.2 don't build cleanly with GCC ≥ 4.8 #321

rdoursenaud opened this issue Feb 1, 2015 · 3 comments

Comments

@rdoursenaud
Copy link
Contributor

Due to http://bugs.python.org/issue17547, python (and hostpython) targets don't build cleanly with GCC ≥ 4.8.

This makes buildozer useless here on my Arch Linux.

Is there any plan to update Python or should I backport the patch ?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@FeralBytes
Copy link
Contributor

Is this a p4a issue or is it really a Python issue, I see the issue you linked and it is mark resolved. So what really is the issue? Sounds to me like an Arch issue as you are waiting for Arch to push the patched versions of Python, is that right?
Also the issue that you reference against buildozer #153 does not seem related to me, because it is a Java Exception that kevinkjt2000 is experiencing, but the python issue from above is a GCC compiler flag error.
I am really just trying to understand better so, please expand as able, thank you.

@rdoursenaud
Copy link
Contributor Author

This is a python-gcc compatibility issue that's bleeding into p4a because of the outdated python version used. It's fixed upstream but not in the version used by p4a.
The buildozer bug may not be related but its p4a build log clearly show the same symptoms I have.

@inclement
Copy link
Member

No longer an issue with the build tools moving to clang.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants