-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Error building pyprocessing on Solaris SPARC after changes to python #8371
Comments
comment:1
The revised spkg can be found at: The Mercurial patch is attached. |
Mercurial patch |
comment:2
Attachment: Solaris-specific-patch-for-pyprocessing.patch.gz |
comment:3
Updating to blocker, as this essential for a succesful Solaris build. However, if #6503 is merged, then this can be ignored, as that intends removing all of pyprocessing. But the ticket is 8 months old. |
comment:4
Closing this as wontfix since #6503 removes pyprocessing from the standard spkg repository. |
== The computer hardware & software ==
== The Sage software ==
Sage 4.3.3 which comes with python-2.6.4.p5 and pyprocessing-0.52.p0
== The problem ==
This is a long story, so I'll keep it short.
Implement 2-isogeny descent over QQ natively in Sage using ratpoints #6583 "Implement 2-isogeny descent over QQ natively in Sage using ratpoints" was integrated into Sage 4.3.1.
The above patch, which was not properly checked on Solaris, broke the Solaris build as reported at GCC reports incorrect flags compiling descent_two_isogeny.c on Solaris 10 #7867
Jaap Spies found this link http://bugs.python.org/issue1759169 which suggests this is a bug in python, which will be fixed in the next 2.6 release. But a patch is provided on the python web site.
remove the pyprocessing spkg from sage, then sort out any fallout that results #6503 is an 8-month old patch to remove pyprocessing from Sage, as the multiprocessing module, which has a slightly different API, is now part of Python 2.6.
The patch at http://bugs.python.org/issue1759169 was integrated into python-2.6.4.p5, but it broke the build of pyprocessing as below
Component: porting: Solaris
Issue created by migration from https://trac.sagemath.org/ticket/8371
The text was updated successfully, but these errors were encountered: