Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
Version 1.9 Build 1556 |
|
AIPS++ installation script.
configure
configure is used as the first step in installing AIPS++, either from scratch, or to add a new architecture (see §2.2) and (§2.3). In the latter case the installation of the aipsinit (p) scripts and databases can be skipped.
A copy of configure resides in aips2.nrao.edu:/pub/aips++/code_ftp on the AIPS++ anonymous ftp server together with the compressed tar files which constitute an AIPS++ installation kit (see §1.1.5 for a description of the AIPS++ ftp directory structure).
Once configure has been activated the installation consists of answering a few questions, most of which have sensible default answers. configure first ensures that certain utilities that it needs are available. These are GNU gzip and GNU make (p). If they aren't it fetches them from the consortium site and if necessary, installs gzip temporarily in the current directory. It then unloads any compressed tar files present in the current directory.
configure next installs the aipsinit (p) scripts and constructs the $AIPSROOT/aipshosts (p) database via a simple inbuilt editor (AIPS++ variable names are listed in §1.2). Once the host architectures, site-name, and host-names are known, configure invokes aipsinit for itself and then creates the AIPS++ system directory tree for each architecture. With a bin directory now in existence, configure reinstalls gzip if necessary, and likewise gmake (p).
Before gmake can be invoked, however, the site-specific makedefs (p) file must be defined. This contains definitions used by gmake for directories, compiler options and the like. Generic definitions are provided in $AIPSARCH/makedefs but several of these have no sensible default and must be defined on a per-installation basis. If none already exists, configure installs a template makedefs (p) file in $AIPSSITE and invites the installer to make the appropriate entries with a text editor in another window (or by suspending configure). When the user is satisfied, configure checks to make sure that all definitions are sensible (see testdefs (p)), and then repeats the process for the site-specific aipsrc (p)).
At this point the system should have been bootstrapped to a state where a recursive gmake may be used to check-out all code and build the system, and this configure now does (see §10).
None.
Construction of the aipsrc databases is part of configure's job.
Status return values correspond to the various phases of the operation
0
: success
1
: initialization error
2
: error fetching required utilities or installing gzip
3
: error extracting compressed tar files
4
: error installing the aipsinit (p) scripts or databases
5
: error constructing the system directory tree
6
: error installing gzip, gmake
7
: error installing local makedefs and aipsinit files
The GNU manual page for gzip.
The GNU manual page for gmake.
AIPS++ variable names (§1.2).
Installing an AIPS++ production-line system (§2.2).
Installing an AIPS++ code-development system
(§2.3).
aipshosts (p), AIPS++ hosts database.
aipsrc (p), AIPS++ resource database.
getrc (p), query AIPS++ resource database.
makedefs (p), AIPS++ makefile definitions.
testdefs (p), test makedefs (p) definitions.
Original: 1992/04/09 by Mark Calabretta, ATNF.