#12789: Move local/bin/sage-check-64 to spkg/bin/sage-arch-env
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: leif
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: scripts | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by leif):
Replying to [comment:10 jdemeyer]:
> Added items 5 and 6.
>
> One idea from #10303 that I disagree with is to source `sage-check-64`
(now `sage-arch-env`) only in `sage-spkg` and `sage-build`, i.e. when a
package is being built. I think it can be useful even within Sage, for
example to compile Cython files.
Well, Cython should take `CFLAGS` etc. from distutils, i.e., Python.
Doesn't really make sense to change the settings (`SAGE64` or whatever)
afterwards or inbetween. Either you do (or have) a 64-bit build, or not.
The original purpose of the `sage-64.txt` file is exactly to avoid mixing
up 32-bit and 64-bit builds (although there are certainly better ways to
achieve this).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12789#comment:11>
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.
