#12369: Add a gcc package
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: tbd
Type: task | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: packages | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: Jeroen Demeyer
Merged: | Dependencies: #12479, #12602, #12608, #12609,
#10492, #12367, #12368, #12405, #12570, #12574, #12423, #12425, #12456, #12363,
#12223, #12515, #12519, #12548, #12562, #12629, #12638
------------------------+---------------------------------------------------
Comment(by SimonKing):
Building the gcc spkg really takes an awful lot of time.
One question: If I want to rebuild Sage with the compiler built by the
spkg, perhaps with additional optimizations (provided that the gcc-spkg is
able to pick up my system-wide `CLooG` or I manage to make a `CLooG`
spkg), how could I do so?
Of course, `sage -ba` would recompile all Cython code in the Sage library,
but it would not re-install the spkgs. Is there an easy way to install all
standard packages from scratch? I am not talking about an automatic re-
installation of the optional packages.
In particular, would it work to remove all entries in
`SAGE_ROOT/spkg/installed` that correspond to standard packages, and do
`make` again? Or perhaps better exempt the `sage*` spkgs from re-
installation, since my Sage library is patched?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12369#comment:108>
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.
