Robert Bradshaw wrote:
Once OpenSolaris is up and running, we could put it in a VM on boxen,
and use it as part of the build farm. Of course that won't be a true
Sparc solaris machine, but unless someone has extra money/hardware
laying around it'll probably be a more realistic solution that waiting
on t2 throughout the whole release management process.
- Robert
To be honest, having Solaris 10 (not OpenSolaris) on a virtual machine now would
probably be a big help now.
There should be minor differences between Solaris 10 on SPARC and Solaris 10 on
x86. There may be some if there is assembler code, which has things like
#ifdef __sun__
/* Include SPARC assembly code */
#endif
since I suspect some of the assembly code for Solaris was written before Solaris
run on x86, so might automatically assume that Solaris has a SPARC processor.
That should only need minor changes. I've not tried building Sage on Solaris 10
(x86) myself, but a Solaris 10, rather than Open Solaris machine could be useful.
There is quite a difference from Solaris 10 to Open Solaris. The latter is aimed
much more for desktop use.
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
