Differences between revisions 55 and 56
Revision 55 as of 2009-12-24 13:47:51
Size: 7065
Editor: DavidKirkby
Comment:
Revision 56 as of 2009-12-24 13:55:12
Size: 7173
Editor: DavidKirkby
Comment:
Deletions are marked like this. Additions are marked like this.
Line 78: Line 78:
This is a bit tricky. It's easier to do than explain, but I'll try to explain how to do it.
Line 86: Line 88:
When gcc is configured, it can be built to use either the Sun or the GNU linker and assembler. Unfortunately, the Sun linker and GNU linker do not use the same options. So code in Sage, which builds shared libraries, needs to know what linker your gcc is configured to use. '''The sage build process makes the assumption that whatever linker gcc is configured to use, will be in your path before any other linker''' So if you use the GNU linker, which is likely to be installed somewhere like /usr/local, then it's essential that the GNU linker is in your path before the Sun linker, which is in the directory /usr/ccs/bin. Conversely, if your gcc is configured to use the Sun linker (which we recommend), then its essential that /usr/ccs/bin is in your path before anywhere that might contain a GNU linker. When gcc is configured, it can be built to use either the Sun or the GNU linker and assembler. Lots of code in Sage builds shared libraries, which need appropiate compiler and linker options. , which builds shared libraries, needs to know what linker your gcc is configured to use. '''The sage build process makes the assumption that whatever linker gcc is configured to use, will be in your path before any other linker''' So if you use the GNU linker, which is likely to be installed somewhere like /usr/local/bin, then it's essential that the GNU linker is in your path before the Sun linker, which is in the directory /usr/ccs/bin. Conversely, if your gcc is configured to use the Sun linker (which we recommend), then its essential that /usr/ccs/bin is in your path before anywhere that might contain a GNU linker.

Running Sage on Sun's Solaris operating system.

This page, which is primarily maintained by David Kirkby, describes the current status of Sage on the various versions of Solaris and on various hardware (SPARC and x86).

Although it is Christmas Eve as I write this, I suspect a Solaris server running Sage will be available before the end of 2009 at http://t2nb.math.washington.edu:8000/ That's a Sun T5240 kindly donated by Sun. But it is not installed just yet, but will be in the next few days.

Solaris 10 on SPARC hardware.

That latest Sage release, 4.2.1, will build on Solaris as long as you do not have Sun Studio installed, though there are a couple of tricks you can use to get it to build if you do have Sun Studio installed.

Sage 4.3 or later, which will be released in January 2010, should build and run on any SPARC hardware which runs Solaris 10. Sage has been built on several Solaris 10 SPARC systems, ranging from old machines to current models and from the first release of Solaris 10 (03/2005 edition) to the latest (05/2009 edition). So Sage should build on your Solaris 10 SPARC machine. Specific hardware/software combinations on which Sage has been built are

  • Sun T5240 CoolThreads server with:

    • 2 x 1167 MHz T2+ Coolthreads processors
    • 16 cores
    • 128 threads
    • 32 GB RAM
    • Solaris 10 update 6 (05/2009 edition).
  • A Sun Blade 2000 workstation with:
    • 2 x 1200 MHz UltraSPARC III+ processors.
    • 8 GB RAM
    • Solaris 10 update 7 (05/2009 release) which at the time of writing (December 2009) is the latest release of Solaris 10.
  • Sun Netra T1 server with:
    • 1 x 500 MHz UltraSPARC-IIe processor
    • 1536 MB RAM
    • Solaris 10 03/2005 (the very first Solaris 10 release).

Sage will run in a Solaris zone, so if you want to make a public access server, with negligible security risks, then you can do so.

There are a few problems with the build on Solaris 10, all of which we hope to resolve.

  • Only GCC >= 4.0.1 can be used to build Sage. Supporting Sun Studio is an aim, but it's unlikely to happen soon.

  • As stated above, if Sun Studio is installed, Sage 4.2.1 will not build. This is easy to fix - more details below.
  • Sage currently only builds in 32-bit mode on Solaris 10.
  • Sage has a large test suite, which is run regularly by Sage developers. Not all the tests pass on Solaris 10. We are looking into reasons why this might be so.

Solaris 10 on x86 hardware.

This has not been tested, but would have a high probability of working. Let us know if you try it.

Open Solaris (also known as Solaris 11) on SPARC hardware

This has not been tested and will almost certainly not work.

We are afraid to say nobody currently developing Sage uses Open Solaris on SPARC hardware. Given the number of users of Open Solaris on SPARC hardware is so small, it is doubtful much effort will be put into a port. But if others wish to submit patches, they can do.

Open Solaris (also known as Solaris 11) on x86 hardware

Unfortunately, as of December 2009, the latest release of Sage will not build on Open Solaris. We are actively working on resolving this.

How to build Sage on Solaris 10 with SPARC hardware

As stated above, this should work, but the process is not as simple as one might like it to be.

Stage `1 - make sure you have a suitable gcc, if not build one or download one

Sage has been built with gcc 4.4.1 and 4.4.2, but should work with any gcc >= 4.0.1 that

Solaris 10 only ships with an old version of gcc (3.4.3), which is not built with Fortran support. Sage needs a newer version of gcc than that, and it must be configured to support Fortran. (I believe the binary from Sunfreeware does not support Fortran). If you do not have gcc >= 4.0.1 with Fortran support, you will need to:

Older releases of Solaris 10 ship with a pretty broken gcc in /usr/sfw/bin. You might need to apply patch 123647 on old releases. Exactly how old, and what version of the patch is not know, but anything released in mid-2008 should be fine. It is highly recommended that you configure gcc to use both the Sun linker and Sun assembler, though Sage should build if the GNU tools are used. A configuration whic is known to work is:

drkirkby@kestrel:~$ gcc -v
Using built-in specs.
Target: sparc-sun-solaris2.10
Configured with: ../gcc-4.4.2/configure --prefix=/opt/kirkby/gcc-4.4.2/ 
--with-gmp=/usr/local/ --with-mpfr=/usr/local 
--with-build-time-tools=/usr/ccs/bin --enable-languages=c,c++,fortran
Thread model: posix
gcc version 4.4.2 (GCC) 

Stage 2 Set up a build environment.

This is a bit tricky. It's easier to do than explain, but I'll try to explain how to do it.

Sage needs the GNU versions of make and tar to build. They must be called make and tar too, and not gmake or gtar. You do not need particularly new versions of these tools, so those in /usr/sfw/bin will be fine. It is suggested you do this as follows

$ mkdir $HOME/bins-for-sage
$ cp /usr/sfw/bin/gmake $HOME/bins-for-sage/make
$ cp /usr/sfw/bin/gtar $HOME/bins-for-sage/tar

When gcc is configured, it can be built to use either the Sun or the GNU linker and assembler. Lots of code in Sage builds shared libraries, which need appropiate compiler and linker options. , which builds shared libraries, needs to know what linker your gcc is configured to use. The sage build process makes the assumption that whatever linker gcc is configured to use, will be in your path before any other linker So if you use the GNU linker, which is likely to be installed somewhere like /usr/local/bin, then it's essential that the GNU linker is in your path before the Sun linker, which is in the directory /usr/ccs/bin. Conversely, if your gcc is configured to use the Sun linker (which we recommend), then its essential that /usr/ccs/bin is in your path before anywhere that might contain a GNU linker.

The easiest way to find out what linker your gcc uses is to type

kirkby@t2:[~] $ gcc -v
Using built-in specs.
Target: sparc-sun-solaris2.10
Configured with: ../gcc-4.4.1/configure --prefix=/usr/local/gcc-4.4.1-sun-linker/ 
--with-as=/usr/ccs/bin/as --without-gnu-as 
--with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++,fortran 
--with-mpfr-include=/usr/local/include --with-mpfr-lib=/usr/local/lib 
--with-gmp-include=/usr/local/include --with-gmp-lib=/usr/local/lib 
CC=/usr/sfw/bin/gcc CXX=/usr/sfw/bin/g++
Thread model: posix
gcc version 4.4.1 (GCC) 

Note in the above the linker is /usr/ccs/bin/ld. If you have a GNU version of the linker around on your system called ld is absolutely essential that the

Stage 3 Type 'make' and wait for Sage to build

Stage 4. Start using Sage!