#17358: Compilerwrapper package enforces GCC installation
-------------------------------------+-------------------------------------
Reporter: jpflori | Owner:
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-6.5
Component: build | Resolution:
Keywords: | Merged in:
Authors: Jean-Pierre Flori | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jpflori/ticket/17358 | 38093124eb01d154c48f6bdf19145519d9c20507
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jpflori):
Replying to [comment:6 jdemeyer]:
> Replying to [comment:5 jpflori]:
> > I did not check when the `install` script is run, but if it is run at
some point after `GCC` installation without `SAGE_INSTALL_GCC=yes`, `GCC`
will never get updated if one of its dependencies is or if a new version
is merged unless `SAGE_INSTALL_GCC=yes` and `install` get run once again?
Am I wrong?
> You are right, but perhaps that isn't a problem. I don't think we need
to treat GCC like other packages. If users have GCC 4.9.1 instead of
4.9.2, that's no problem. And if it would be a problem, we just blacklist
GCC version 4.9.1 (for all setups, including system GCC 4.9.1).
I agree with that.
So the only problem left is what if MPIR or another GCC dependency gets
updated to a binary incompatible version (or let's say the symlinks ends
up with different names)?
--
Ticket URL: <http://trac.sagemath.org/ticket/17358#comment:9>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
