On Jul 9, 2009, at 2:20 PM, William Stein wrote:
> > On Wed, Jul 8, 2009 at 9:51 PM, William Stein<wst...@gmail.com> wrote: >> Hi, >> >> In case anybody wants to try out 64-bit Sage on OS X, I posted a >> binary here: >> >> >> http://wstein.org/home/wstein/binaries/sage-4.1-OSX-10.5-Intel-64bit-i386-Darwin.dmg >> >> Sage almost builds out of the box on 64-bit OS X, except scipy and >> ratpoints both fail, and >> one has to install a fortran spkg that supports 64bit. See >> >> http://trac.sagemath.org/sage_trac/ticket/6493 >> >> (I've fixed both scipy and ratpoints, but refereeing is needed.) >> >> 64-bit Sage on OS X is *much* faster than 32-bit in many cases, >> especially code that relies on MPIR (where a 3-times speedup is not >> unusual). >> >> -- William > > Moreover, I just tried and the full test suite passes too. Yeah! > > The only thing that is in the way of making 64-bit the standard for OS > X Sage is: > (1) auto-downloading the gfortran spkg or something > (2) getting the above two spkg's positively reviewed and into Sage. > > Even the notebook works fine now, since we upgraded to python 2.6.x > (this was a problem before). > > If you're an intel OS X user and you haven't got excited about 64-bit > Sage, why not?!?! > > -- William I've been looking forward to it for some time. I'm currently running the test suite before I start using it as my regular Sage version. Thanks! Is there anything specific we need to do for python extensions to get them to build in 64-bit if we want to include them in our Sage scripts? Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo http://www.linkedin.com/in/timlahey --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
