On Fri, Feb 10, 2012 at 19:46, firebird wrote:
> Tried Dima's suggestions to cut down compute time
> (a) SAGE_ATLAS_ARCH=CoreI7,SSE3,SSE2,SSE1... unfortunately rejected??
I think that needs to be be SAGE_ATLAS_ARCH=Corei7,SSE3,SSE2,SSE1
(note the capitalization of the i).
> Though GAP was preins
Hi all
Thanks for your support! And yes, the build worked.
Tried Dima's suggestions to cut down compute time
(a) SAGE_ATLAS_ARCH=CoreI7,SSE3,SSE2,SSE1... unfortunately rejected??
(b) Tried Loading Ubuntu Atlas package. Couldnt find one.
(c) Tried Installation manual trick for Ubuntu installs.
FYI, SAGE_PARALLEL_SPKG_BUILD is deprecated since
http://trac.sagemath.org/sage_trac/ticket/11959 was merged (4.8.alpha0).
Sage currently builds SPKGs in parallel by default. To turn this off you
would need to edit $SAGE_ROOT/spkg/parallel_make.cfg .
-Keshav
Join us in #sagemath on irc.fr
Did the build work? (Maybe I need to wait 7 more hours for an answer.)
I use Ubuntu 11.10, 64 bit, and I have a core i7-2600. I think building
Sage using many processes usually takes me about 2 hours + 15 minutes,
where the 2 hours is all ATLAS, and the 15 minutes is everything else. I'm
building
On Thursday, 9 February 2012 22:02:29 UTC+8, firebird wrote:
>
> Thanks Jason/Volker
>
> Will persevere... Type of computer is I5-2320 Quadcore... Not on your
> list of known processors.
> Will try and find how to save tuning information after next test.
> I am getting the message that compil
Thanks Jason/Volker
Will persevere... Type of computer is I5-2320 Quadcore... Not on your
list of known processors.
Will try and find how to save tuning information after next test.
I am getting the message that compilation will take many hours. So I
will give it 12-24 hours.
I guess that I am com
On Wed, Feb 8, 2012 at 10:27 AM, Jason Grout
wrote:
> On 2/8/12 10:39 AM, firebird wrote:
>>
>> Thanks for the prompt response, but it is barely credible...
>
>
> Atlas will sometimes do tuning, which means that it will run the same
> program lots of times with different values in order to ascerta
On 2/8/12 10:39 AM, firebird wrote:
Thanks for the prompt response, but it is barely credible...
Atlas will sometimes do tuning, which means that it will run the same
program lots of times with different values in order to ascertain
exactly what parameters to use to get the fastest linear alg
Looks normal to me. Occasionally ATLAS prints some progress status, that
would be more interesting to grep for.
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit t
Volker
Thanks for the prompt response, but it is barely credible...
Enclosed are some of the more common lines (with frequencies at the
front) from install.log. Is this what you would expect? 169
compilations of the same file? I terminated the job after that.
526 make[10]: Leaving directory
ATLAS will not loop (though it takes almost forever and may fail to
compile). You need more patience ;-)
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this gro
Thanks!
Sage-4.7.2.alpha4 works.
On Oct 12, 4:15 pm, Volker Braun wrote:
> I'm pretty sure we have this compile error fixed in Sage-4.7.2.alpha4.
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@google
I'm pretty sure we have this compile error fixed in Sage-4.7.2.alpha4.
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/gro
13 matches
Mail list logo
