#7505: Add scripts which check C and C++ compilers, and report what they are.
---------------------------+------------------------------------------------
Reporter: drkirkby | Owner: tbd
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.3.1
Component: build | Keywords:
Work_issues: | Author: David Kirkby
Upstream: N/A | Reviewer:
Merged: |
---------------------------+------------------------------------------------
Changes (by drkirkby):
* cc: was (added)
* priority: minor => major
Comment:
The review of this has got a bit complex, mainly since agreeing where the
scripts should go has not been without some problem, but I also slightly
changed the output shown, in view of difficulty of the fact Sun Studio can
be run on Solaris, and difficulties finding some information I wanted.
Hence I thought I'd clarify some things.
The scripts output one of:
* GCC
* Sun_Studio
* HP_on_Tru64
* HP_on_Alpha_Linux
* HP_on_HP-UX
* IBM_on_AIX
* Unknown
I believe the scripts (see attached) should be:
{{{
$SAGE_ROOT/spkg/base/testcc.sh
$SAGE_ROOT/spkg/base/testcxx.sh
}}}
The file
{{{
$SAGE_ROOT/spkg/install
}}}
needs to be modified (patch attached), so it copies the two scripts to
{{{
$SAGE_LOCAL/bin
}}}
in addition to the files it already copies there. This allows the scripts
to be called from anywhere, including the prereq script, which might be
necessary.
The scripts can't actually break anything in Sage, as they are not called
at all. But calling them will simplify a lot of portability issues later
one.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7505#comment:14>
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.
