On Thu, Apr 15, 2010 at 9:37 AM, John Cremona <john.crem...@gmail.com> wrote: > Atlas is supposed to find out what sort of processor your machine has > automatically and then use tuning data for that. But it is not > perfect at detecting the processor type, so then it goess of to do > this tuning stuff which takes hours. The same happened to me when I > got a new laptop in 2008. Until Sage upgraded Atlas the only was I > found to stop this (very) time-consuming step happening for every Sage > build (often unsuccessfully) was to keep the previous successful > build. > > Once you have a good build of Atlas, take a copy of SAGE_ROOT/local; > and set SAGE_ATLAS to point to that copied directory. then when you > build Sage it will use that copy of Atlas instead of rebuilding it. > > John > > On 15 April 2010 17:28, Bruce Cohen <math.co...@gmail.com> wrote: >> I now remember that I did have a 5 hour scp file transfer running that >> night. It is a brand new machine, so I was bringing over a tar file >> from an old machine on my network. I will try again tonight. It is >> disappointing that that the new quad core i7 (purchased to do Sage >> work) could not handle two tasks. We'll see.
If that doesn't work, you might try building after first typing export SAGE_FAT_BINARY="yes" This will result in a Sage that is non-optimal at numerical linear algebra computations. But ATLAS will I think be much more likely to build, since it just uses some minimal default configuration. William -- 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 To unsubscribe, reply using "remove me" as the subject.
