Dave, this is meant to be MacOSX-specific, for testing of the concept. If this flies on 10.x for x!=5, with hardware not necessarily PPC, then we are in business and can go this way.
Dima On Sep 12, 4:35 pm, David Kirkby <david.kir...@onetel.net> wrote: > On 12 September 2010 08:33, Dima Pasechnik <dimp...@gmail.com> wrote: > > > > > On Sep 12, 2:38 am, Dima Pasechnik <dimp...@gmail.com> wrote: > >> I got stuck at scipy: > > > I have fixed this by making changes in numpy's patch for gnu.py. > > The complete build of Sage-4.5.3.has successfully finished now. > > I'll post the necessary patched, and the test results, shortly. > > It would be good if you could not hardcode gfortran but left the > possibility of using other compilers - i.e. do use the variable > SAGE_FORTRAN. > > or better still, use FC, but set > > FC=SAGE_FORTRAN > > Them one day perhaps we can just remove the SAGE_FORTRAN variable;e > amd use FC like everyone else. > > Some parts of Sage will build with the Sun Fortran compiler, so I'd > like to keep that possibility of at least invoking that. > > Dave -- 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
