On 1 February 2011 20:17, jtyard <jty...@gmail.com> wrote: > Thanks Georg, > > Before I posted my question, I had tried an earlier build with > SAGE64="yes", but (of course) that didn't work and I received the same > error that I posted. Then I had set SAGE64="no", tried again and got > the same error.
There is never any point in setting SAGE64=no. All the bits of code in Sage which make use of the variable SAGE64 are written to check if it is "yes" - all in lower case. So setting it to "YES", "no", "NO", "foobar" or unsetting it all have the same effect. ONLY if it is set to "yes" will anything different happen. That is usually adding the compiler flag "-m64", though in some cases it's a bit more complex. To my knowledge, this variable is only needed on older versions of OS X, and all versions of Solaris. However, there is generally no code that checks the operating system and SAGE64 at the same time, though there are the odd exceptions. (There used to be lots which checked if the variable was set to "yes" and the operating system was OS X, but that has all been removed, so the variable SAGE64 works on Solaris where it is needed now, and would also work on HP-UX or any other platform where binaries default to 32-bit, but can be 64-bit.) 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
