#10303: clean up sage-check-64 and use of SAGE64
-----------------------------+----------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-4.6.1
Component: build | Keywords: 64
Author: John Palmieri | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by leif):
Replying to [comment:18 leif]:
> And it doesn't make any sense to mess with `SAGE64` and flag files on
systems not defaulting to 64-bit builds, unless or until we also support
the opposite, 32-bit builds on systems that default to 64-bit.
Should of course read ''"on systems defaulting to 64-bit builds"'' (or
''"'''not''' defaulting to '''32-bit''' builds"'').
[[BR]]
> > > Do you think we should print a warning saying that it might not be
fully supported, or just accept SAGE64=yes silently on platforms other
than OS X and Solaris?
> >
> > I don't feel the need to print any message it's unsupported.
>
> Because of its bad name, people erroneously set `SAGE64` in the past.
Note that there are (still) spkgs around that do more than just adding
e.g. `-m64` if `SAGE64=yes`, i.e. setting it at least currently has other
side effects.
So giving an error message on unexpected (and therefore unsupported)
situations makes sense to me.
We could suppress such messages if `SAGE_PORT` is non-empty.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10303#comment:19>
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.
