It's taken more than 12 hours to build ATLAS on t2, and it is still going. William said it takes a lot less if some tuning parameters are known for the machine, so it does not have to go through that again. I asked on the ATLAS help forum, but so far no reply for how to save these parameters.
So a few question. 1) Does anyone know how to save the parameters for a machine, or just force ATLAS to use a semi of semi-sensible defaults. 2) Does anyone know how I can save the binaries and restore them another time, rather than rebuild it. Sage releases are comping out quicker than I can build it on Sage, due mainly to the very long time to compile ATLAS. It takes nowhere near as long on my own SPARC, so I believe it's probably since mine is a lot more common than 't2', so perhaps there is data on my machine, but not t2. Any other suggestion - apart from buy a turbo charger? It would be good if some of the other packages could be built in parallel. There is no reason one could not build the next package, assuming that does not depend on ATLAS. Dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
