The SAS proper tar files have names like
xmmsas_yyyymmdd_hhmm.tar.gz
. When unpacked, this creates
the directory xmmsas_yyyymmdd_hhmm
.
The additional-libraries tar files have names like
xmmsas_yyyymmdd_hhmm_libextra.tar.gz
. They must be
unpacked in the directory xmmsas_yyyymmdd_hhmm
.
/path/to/xmmsas_yyyymmdd_hhmm
, then
. $SAS_DIR/sas-setup.sh
(or source
$SAS_DIR/sas-setup.csh
).
You are ready to run the SAS. Type sashelp
to start
Netscape on the SAS documentation. If that does not work, point your
browser to $SAS_DIR/README.html
.
To start the SAS task launcher type sas
.
Make sure you also have installed and configured the required software packages.
An important step in the SAS build process consists in setting up the correct Unix environment. Achieving this may not be trivial, especially if you expect to be able to use at the same time other software packages that may contain or require conflicting libraries.
With a wrongly configured environment, packages may fail to work or even build correctly. The SAS configuration script (see below) will spot most environment problems before you start the compilation. Other problems may emerge during the build stage.
If you cannot proceed, first consult the SAS main page, where you also find instructions on how to submit a problem report and get help with the installation.
The SAS configuration makes use of the following environment variables:
PATH
: the executables required to compile the SAS
(the compilers, make, etc.) must be found first in the list of
directories listed. If in doubt use the Unix command
which
(C shell) or type
(Bourne shell)
to determine which executable is being picked up by the
configuration script.C_INCLUDE_PATH
and CPLUS_INCLUDE_PATH
:
these variables must contain a colon-separated list of
directories where to find the header files of the packages
external to the SAS (e.g., CFITSIO and Qt). The same list of
directories should appear in both variables because the SAS
makes use of both the C and the C++ compilers.LIBRARY_PATH
and LD_LIBRARY_PATH
:
these variables must contain a colon-separated list of
directories where to find the libraries of the packages external
to the SAS (e.g., CFITSIO, Qt, the Fortran compiler
library). The first variable lists the directories where to
find static libraries (name usually ending with .a
); the
second lists the directories where to find shared libraries
(names usually ending with .so
).
/usr/local/sas
.
cd /usr/local/sas
./configure
config.log
where it reports the detailed, if
somewhat cryptical, reasons why some software package was not found.SAS_DIR
to
/usr/local/sas
; set the environment variable
SAS_CCF
to be equal to
$SAS_DIR/lib/testccf
; set the environment variable
SAS_ODF
to be equal to
$SAS_DIR/lib/testodf/scisimsimple
.
. $SAS_DIR/sas-setup.sh
for Bourne-like shells
(sh, bash, ksh)source $SAS_DIR/sas-setup.csh
for C-shell-like shells (csh, tcsh)make check
check.html
will contain a summary of what packages were built, with
links to any errors that might have occurred. The file
evaluatebuild.html
explains if some packages fail
indirectly, that is, because one of the packages they depend on
fails.
$SAS_DIR/README.html
. Type
sas
to start the SAS task launcher.
check.html
to a text file
containing the full details of the build of a particular package: this
should give you an idea of what went wrong. Try to correct the
problem, if you think this could be due to a misconfigured
environment.
If you think you have identified a problem, see the SAS main page for further
advice. There you find also instructions on how to submit a problem
report.
Software requirements
The following software packages must be installed correctly in order
to build the SAS from sources. When a package version number is
specified, this means that the SAS development team makes use of that
particular version. Newer or older versions may still work, but have
not been tested.
To build the documentation, the following software is also needed: