Installation from source is very easy, because the distribution contains everything on which SAGEdepends.
http://modular.fas.harvard.edu/SAGE/dist/src/index.html
gunzip sage-*-src.tar.gz tar xf sage-*-src.tar
tar zxvf sage-*-src.tar.gz
on many systems.
sage-*
.
cd sage-*
make
make install
as described below.
After you build SAGE, you may optionally install the result to
/usr/local
using su; make install
. If you do this, a
directory /usr/local/sage/sage-version
is created and the parts
of SAGEthat you built are copied there. Also, the two files
sage
and sage-version
are placed in
/usr/local/bin/
. If you install a future version of SAGE, the
old version(s) will still be available via the command
sage-version
. To install to a different prefix than
/usr/local/
, modify the file source/prefix
.
./sage
SAGE Version *.... Copyright (C) 2005 William Stein <was@math.harvard.edu> Distributed under the terms of the GNU General Public License (GPL) sage:
sage: factor(2005) _1 = 5 * 401
echo $PATH
and cp sage <your-path-dir>
into one of these directories,
or else add this bin
directory to your PATH variable,
e.g., if you use the bash shell, add the line
PATH="<sage-home-dir>/bin":$PATH export PATH
make test
.
This runs all examples in the API documentation and makes
sure that they run exactly as claimed. In a few cases there
may be some discrepancies because, e.g., 64-bit machines
print float numbers to higher precision than 32-bit.
rm -rf install/build
make clean
.
Have fun!
Note: The subdirectory called log contains the logfiles and conf contains the IPython configuration file used by SAGE. The
logfiles log every command (not the output) you type in, and the
history is persistent between sessions. There is also a file called
log/verbose, which is where verbose logging goes when you use
the set_verbose
command in SAGE.
See About this document... for information on suggesting changes.