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 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.
>
> -Bruce
>
> On Apr 15, 7:51 am, Bruce Cohen wrote:
>> The job ran overnight and nothing else was going on. Perhaps I
>> should try again tonight.
>>
>> -Bruce
>>
>> On Apr 14, 11:18 pm, Robert Bradshaw
>> wrote:
>>
>>
>>
>> > On Apr 14, 2010, at 11:12 PM, Bruce Cohen wrote:
>>
>> > > I have a new machine with Ubuntu 9.10 (32 bit). My first build of
>> > > Sage (4.3.5) did not work. Here is a 100 line (maybe too many lines,
>> > > maybe too little) of install.log.
>>
>> > > Thanks for your help.
>>
>> > > -Bruce
>>
>> > How loaded is your machine?
>>
>> > > make[3]: *** [build] Error 255
>> > > make[3]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/
>> > > atlas-3.8.3.p12/ATLAS-build'
>> > > make[2]: *** [build] Error 2
>> > > make[2]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/
>> > > atlas-3.8.3.p12/ATLAS-build'
>> > > Failed to build ATLAS.
>> > > ATLAS failed to build for the 1-th time, possibly because of a
>> > > loaded system, so we will automatically try again up to 4 more times.
>> > > Waiting 9 minutes...
>> > > ATLAS failed to build for the 2-th time, possibly because of a
>> > > loaded system, so we will automatically try again up to 3 more times.
>> > > Waiting 10 minutes...
>> > > ATLAS failed to build for the 3-th time, possibly because of a
>> > > loaded system, so we will automatically try again up to 2 more times.
>> > > Waiting 10 minutes...
>> > > ATLAS failed to build for the 4-th time, possibly because of a
>> > > loaded system, so we will automatically try again up to 1 more times.
>> > > Waiting 7 minutes...
>> > > Too many failures to build ATLAS. Giving up!
>>
>> > ATLAS seems to be having issues getting reliable timings for its tuning.
>>
>> > - 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
>
> To unsubscribe, reply using "remove me" as the subject.
>
--
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
