On Sat, Aug 1, 2009 at 4:19 PM, Peter Jeremy<peterjer...@optushome.com.au> wrote: > On 2009-Aug-01 20:22:09 +0100, Jason Moxham <ja...@njkfrudils.plus.com> wrote: >>So are you saying that the compilers on T2 are broken in 64bit mode ? or just >>sage is broken ? or just mpir ? or dont we know? > > Sun development tools treat Solaris as "primarily a 32-bit OS but you > can build 64-bit applications if you jump through the right hoops". > This differs from 64-bit versions of Linux and FreeBSD where the > toolchain builds 64-bit applications by default and you need to jump > through hoops to build 32-bit applications. > > In my experience, actually building 64-bit applications on Solaris is > frustrating because configure scripts generally assume 32-bit and much > of the prebuilt freeware is 32-bit only. It usually comes down to > telling an application to build in 64-bit mode and then when one of the > link steps blows up with the "wrong ELF class" error, working back to > find which dependency is wrong and why it didn't obey the "-m64" or > equivalent. >
OS X is similar in that 32-bit is the default, but one can coerce code into building 64-bit. And thanks entirely to Michael Abshoff there is a 64-bit port of Sage for OS X which works. So when we do the 64-bit port of Sage for Solaris we can look at the code for OS X 64-bit in each spkg-install as a guide. And fortunately the infrastructure (mainly a SAGE64 flag) is in place for building 64-bit Sage on at least one "32-bit by default" architecture. -- William --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
