On 7 Okt., 23:44, "Dr. David Kirkby" <david.kir...@onetel.net> wrote:
> Thank you, I see the point of saving SAGE64 now.
>
> Does the same not apply to ALL other variables like CC, CXX,
> SAGE_FORTRAN .. etc too? I believe I have screwed up builds by mixing
> compilers.
Wouldn't it make sense to create a file that stores and documents the
*complete* (or all relevant) settings that were used when building
Sage?
When upgrading, sage-env could look up the old settings and determine
whether it is compatible with the current settings, and either adopt
the old ones (say, SAGE64 was used when building Sage, so it *must* be
used when upgrading), or issue a warning if the new settings are
different but are likely to work (say, -O1 was used when building
Sage, but now -O2 is being used for upgrading).
Cheers,
Simon
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
