#10430: Add some bugfixes to the PARI package
------------------------------+---------------------------------------------
Reporter: jdemeyer | Owner: tbd
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.6.2
Component: packages | Keywords: pari spkg bugs patches
Author: Jeroen Demeyer | Upstream: N/A
Reviewer: Leif Leonhardy | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by vbraun):
> I totally agree with this by the way, but in my opinion there are two
things we can do:
> 1. Use -O3 always and leave the user with a non-compiling Sage ("it's
not our fault, it's gcc's fault")
> 2. Do the optimization-fallback as in this spkg.
3. Show the error and then tell the user how to report the issue and
continue the build without optimization. I think all thats needed is
{{{
CFLAGS=-O0 ./sage -f spkg/standard/pari*
make
}}}
to build pari with no optimization and then build the rest?
> I believe making a blacklist of versions known to fail is not a good
solution because there will always be systems with a broken gcc that we
don't know of.
But if we silently try some workarounds then we will never find out about
broken compilers either. The user should file a trac ticket to document
the issue so it can be fixed in Sage and reported upstream.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10430#comment:43>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
