On 08/19/2013 07:36 PM, John Cremona wrote:
What would make atlas suddenly decide to start running its tuning code
(building 5.12.beta1) on a machine which a few days ago built 5.11
without that happening? It's frustrating since even though I am using
make -j32 the tuning code is taking forever...
Would killing the make and rerunning it save time or just risk
restarting the tuning process from scratch?
John
Well, you have run into the problems I have been facing (see my posts on
sage-git). It never finishes tuning. Last time I checked it was going on
for two days, and I just decided to kill it and instead compiled sage on
a different machine. I now feel that I should just compile sage on
cloud.sagemath and do my development from there because it is so fast.
My only other nice option is an ultrabook, which may or may not be able
to sustain long compile times and the heat it generates.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
