On Wed, Oct 7, 2009 at 10:53 AM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > > I can see the above file is called from sage-env, but I'm trying to work > out exactly that the aim of it is. Do we really need the script at all? > > It seems to do 3 things. > > 1) If SAGE64 is yes, it prints we are building 64-bit on Solaris or OS X. > > 2) Creates a file called SAGE_LOCAL/lib/sage-64.txt if SAGE64 was set to > yes. Is that file used by anything else? > > > 3) Checks if the file "$SAGE_LOCAL"/lib/sage-64.txt exists, and if so > sets SAGE64 to "yes". > > I really can't see the point in creating this file > SAGE_LOCAL"/lib/sage-64.txt The documented way to make a 64-bit build is > to set SAGE64 to "yes", so its unlikely someone will want to force it to > that by creating the file. > > > Perhaps I'm overlooking the importance of this file.
You are definitely overlooking the importance of this file! Imagine the following incredibly common scenario: 1. You type 'export SAGE64="yes"' and build sage. 2. You come back later and do "./sage -upgrade". Without that file sage-64.txt, you'll suddenly be building in 32-bit mode and everything would be completely broken! Not good. -- William > > If it does no more than I think it does, then it might as well be > ignored and the 'echo' statements put in sage-env. > > > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
