#12369: Add a gcc package
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: tbd
Type: task | Status: new
Priority: major | Milestone: sage-5.0
Component: packages | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: Jeroen Demeyer
Merged: | Dependencies: #11073, #10492, #12366, #12367,
#12368, #12405, #12416, #12422, #12423, #12425
------------------------+---------------------------------------------------
Comment(by rohana):
Replying to [comment:30 jdemeyer]:
> If it gets built, it will be on the critical path (since it effectively
blocks the build).
But you also need to consider that we are building the mpir and mpfr twice
as well as adding one copy of those builds to the critical path. I still
think there is value to distinguishing between when gcc is needed, and
when only fortran is needed. In the latter case, this should actually
negligibly shorten the critical path (with the removal of the fortran
spkg) plus mpir+mpfr don't have to be rebuilt.
My concern is that sage already takes a good while to build, and this spkg
adds a fairly significant time to that for only a few feature gains and
relatively minor performance gains (compared to implementing new/better
algorithms).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12369#comment:33>
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.
