A status report: Last yesterday's build died with ATLAS -- this time on a truly quiet machine. I tried again with a
make clean export SAGE_FAT_BINARY="yes" make but that also died with ATLAS. -Bruce On Apr 15, 10:40 am, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Apr 15, 2010, at 9:28 AM, Bruce Cohen 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. > > That would probably do it. It's probably not a question of being > overloaded so much as being inconsistently loaded, making the ATLAS > timing/tuning parameter graphs to erratic to optimize against. The > suggestions on this thread are good if you're not able to get it going > tonight. > > - Robert -- 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
