#17375: Maxima should not need a working C compiler to run
-------------------------------------+-------------------------------------
Reporter: pbruin | Owner:
Type: defect | Status: positive_review
Priority: blocker | Milestone: sage-6.5
Component: packages: | Resolution:
standard | Merged in:
Keywords: maxima | Reviewers: Karl-Dieter Crisman
Authors: Peter Bruin | Work issues:
Report Upstream: Reported | Commit:
upstream. No feedback yet. | 203767dd8a46873d41df73693739338cc61d85d6
Branch: | Stopgaps:
u/pbruin/17375-maxima_compile |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by pbruin):
Replying to [comment:3 kcrisman]:
> I'm happy with this, it solves the problem of the extra messages and
hence presumably the compiler, passes tests, ''and'' I have tested that
moving the Sage gcc out of the way when this is not applied causes the
problem with `GAZONK` when running `sage -maxima`, but doing so after this
branch is applied causes no problems.
Thanks for the quick review!
> So I think we are cool here. Anything I might have missed? Again, I
think it is quite reasonable to have a bug fix with just this commit
cherry-picked as Sage 6.4.1 (after all, no new spkg needed) while ''also''
including this in the normal Sage 6.5.beta1 so as not to worry about
history.
This also sounds good to me.
--
Ticket URL: <http://trac.sagemath.org/ticket/17375#comment:4>
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.
