William Stein wrote: > 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
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. It says at the top of that file: # Eventually Linux PPC on the PS3 might need to be added here I've no idea what PS3 is (Playstation 3)? I'd like to add AIX, HP-UX, Tru64 and IRIX there - primarily since I have machines that could do build on all of those. I'm not sure if some of them might be 64-bit only. I know the HP will build both 32 and 64-bit, but I'm less sure about the others. On a related issue, sage-env is not run until after bzip is built. But bzip uses position independent code (-fPIC option for gcc), so ideally it would be good to run sage-env earlier on in the build process, so the appropriate flag for position independent code was known. Could that be done? Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
