#13533: Remove "optional - gcc" from doctests
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.4
Component: doctest | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
Replying to [comment:2 kcrisman]:
> Maybe it's not obvious we should force people to have gcc to run
doctests?
The problem is that there are quite a few doctests ''already in Sage''
which require a C/C++/Fortran compiler. So we certainly could mark all
those "# optional - foo compiler". But then a lot of tests would be
missed in normal doctesting. For example, #12446 would not have happened
if the "# optional - gcc" wasn't there.
I think it's not too much to ask for a user to have binutils installed in
order to run Sage doctests. Why only binutils? If #13515 is merged (which
will happen, since it's a blocker), we can ship all the needed
''compilers'' with Sage, which means the host system only needs to provide
binutils (compiler, linker, archiver...)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13533#comment:3>
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.
