Minh Nguyen wrote:
> Hi David,
> 
> On Wed, Jul 15, 2009 at 9:06 PM, Dr. David
> Kirkby<david.kir...@onetel.net> wrote:
> 
> <SNIP>
> 
>>>>> polybori-0.5rc.p9.spkg at
>>>>> http://sagetrac.org/sage_trac/ticket/6437
> 
> I'm still reviewing this ticket. I've started rebuilding a fresh copy
> of Sage 4.1 from scratch on t2 with these updated spkg's:

Good. Sage does not build completely for me, but if will be interesting 
if your attempt fails as the same point as mine, which is

'There was an error installing modified sage library code.'


I can't work out what the error message is on about - the compiler seems 
to think the code is not valid C. I get a failure at the same point at 
home as well.

> [1] pari-2.3.3.p1.spkg
> http://trac.sagemath.org/sage_trac/ticket/6445 [positive review]

Thank you

> [2] ntl-5.4.2.p9.spkg
> http://trac.sagemath.org/sage_trac/ticket/6380 [positive review]

Thank you once again.

> [3] zn_poly-0.9.p1.spkg
> http://trac.sagemath.org/sage_trac/ticket/6443 [positive review]

and again. Getting 3 or 4 Solaris fixes in Sage 4.1.1 will be a great 
help towards getting it building properly on Solaris. There are still a 
number of outstanding issues.

> [4] polybori-0.5rc.p9.spkg
> http://trac.sagemath.org/sage_trac/ticket/6437 [still reviewing]

It's unfortunate you will have to wait for atlas to build. I wish I 
could work out how to save the intermediate files. If I could, I could 
save the architecture specific tuning parameters and build atlas in a 
lot less time.

It's also unfortunate the NFS shared disks are slow. You might consider 
building in /scratch, which is a local disk on t2, or /tmp. Obviously 
/tmp is not backed up, but neither is /scratch too.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to