OptIPortal and SAGE 3
To run SAGE 3 with Rocks 4.3, the following steps are required:
- Install prerequisite packages
- Add the SAGE 3 code
- Patch the SAGE 3 code
- Build SAGE 3 (including initialization of SAGE environment)
1. Install prerequisite packages
The particular additional packages to install will depend on which Rocks
rolls have been installed. The following packages are based on a minimal
installation (kernel, base, os1, os2, hpc, web, viz & hiper rolls). More
extensive installations e.g. everything from the DVD installer, will have many of these packages already installed.
- install quanta rpm from http://www.vislab.uq.edu.au/research/optiputer/sage/rocks/
- install freeglut-dev rpm form rocks os-3 roll
- if "hiper" roll (CGLX) is not installed, build & install glew library
- install alsa-lib-devel rpm from os-4 roll (needed by SDL-devel)
- install SDL-devel rpm from os-3 roll
- install libexif-devel from os-3 (needed by ImageMagick-devel)
- install libtiff-devel from os-5
- install libxml2-devel from os-5
- install ImageMagick-c++-6.0.7.1-17.x86_64.rpm from os-3
- install ImageMagick-devel-6.0.7.1-17.x86_64.rpm from os-3
- replace existing wx-2.6.1.0-1 (its faulty) with
this rebuilt wx package.
Note that because both old and new wx packages have the same version number,
the old installed version must first be uninstalled:
rpm -e wx
Then install the new wx package.
- install external mpeg2 packages:
mpeg2dec and
mpeg2dec-devel
2. Add the SAGE 3 code
- download
sage svn tarball
(OR checkout SAGE directly from EVL's svn repository)
- the tarball (or svn checkout) should be
unpacked in an ordinary user's home directory (typically, the user account used to run the OptIPortal)
- make some symbolic links in this user's home directory
ln -s sage3.0-svn4711 sage3.0
ln -s sage3.0 sage
3. Patch the SAGE 3 code
- download
sage patch
- apply the patch (from the user's home directory)
cat patch-sage3.0-r4711-rocks-4.3 | patch -p0
NOTE the patch specified here relates to
svn checkout revision 4711 which is what is contained in the tarball. If a new
svn checkout is used, the patch file may require changes to apply cleanly!
4. Build SAGE 3
- first, download this
snippet for bashrc file
- add it to the user's ~/.bashrc file
cd
cat bashrc_addition >> .bashrc
- exit any terminal and start a new one in
which to build the SAGE environment
- build the SAGE environment
cd sage
make install
- all going well, a bunch of new applications
will have been installed in the bin directory i.e.in ~/sage/bin/
There's general SAGE configuration to be done now, but thats another story!
Here is the startup script which we use to to start up
the SAGE environment (don't change its name - it knows who it is). It starts
up the connection & file managers, before starting up the SAGE gui. If you make
a hard link from startupSage.sh to stopSage.sh, stopSage.sh can then be used to
cleanly shut down the SAGE environment.
