On Monday, March 31, 2014 4:23:31 PM UTC+2, Dr David Kirkby wrote: > > On 30 March 2014 13:56, Jean-Pierre Flori <[email protected] <javascript:>> > wrote: > > > It would be nice to confirm a 64 bit build is working. > > Just set SAGE64=yes and rebuild everything. > > As far as I remember, the only package not taking this env var into > account > > was the GCC spkg. > > And ATLAS did not manage to use a priori good settings. > > See > > > http://trac.sagemath.org/wiki/ExoticPorts#SunUltrasparcT2runningSolaris1064bitkernel32bituserland64bitSagebuild > > > > > Cheers, > > JP > > There is no need to build a 64-bit version of gcc on SPARC in order to > create 64-bit binaries. A simple 32-bit build of gcc will create > 64-bit binaries if passed the -m64 flag. > Sure, if you already have a correct gcc hanging around somewhere that will do it. If not, then you'll typically want to let Sage build its own, but then it will build 64 bit version of MPIR/MPFR/MPC, and fail to build a 32 bit GCC.
> > I have managed to build a 64-bit version of Sage some time ago (more > than a year), but it was very unstable. I think I was able to compute > 1+1, but that was about it. It crashed quite easily. If I recall > correctly, Pynac was causing some issues. > > > I tried that again recently and it looked quite sane. Not sure I ran the full testsuite though. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
