#10738: insecure temp file in testcc.sh, testcxx.sh
-----------------------+----------------------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: new
Priority: minor | Milestone: sage-4.7
Component: scripts | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by vbraun):
I agree with Dave that currently the best (easiest) option is to just put
the temporary file in a location that only the user compiling Sage can
write to.
In the long run, we should have some common configuration options that are
detected once and then used by every spkg. With canonical names for
different supported C/Fortran compilers, linkers, OSes, architectures.
When I rewrote the ATLAS configuration (#10226) I had that in the back of
my mind and split all the detection code in a `configuration.py` module.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10738#comment:8>
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.
