Next: 2.2 Other information Up: 2 Installation procedure: UNIX Prev: 2 Installation procedure: UNIX Contents
The installation is performed with the help of a Makefile and can be subdivided into two steps:
This step is performed by initiating the following command after reading the magnetic tape:
After entering this command an error message of the following form will probably appear:
La variable MR n'est pas initialisee dans le fichier Makefile Elle doit avoir pour valeur /udd/modulef make: *** [verification] Error 1
In this example, let us assume that the MODULEF cartridge was read into directory /udd/modulef. Variable MR, in file Makefile located in the current directory, must then be initialized to the directory name where MODULEF was read (in this example /udd/modulef).
Having done this, you can re-enter the same command:
As long as variable MR is not initialized correctly, the same type of error message as shown above will appear and the installation will not be effected.
Once the variable is initialized correctly, the Makefile requests the name of the type of machine on which the installation is to be done. A list of names of several type of machines will appear on the screen to aid you with the response. Your response is very important as it initializes variable MM which, amongst others, is used to select the library containing the utilities corresponding to the machine specified. If your machine does not appear in the list, you will need to rewrite the utility corresponding to your machine by consulting libraries u_mod and u_rs6000 (see section 4.2).
Once MM is initialized, the Makefile performs the following actions:
The file Makefile contains the installation Makefile. All the variables necessary for installation are initialized by default in the file M_config (which is read by the Makefile).
Having performed these tasks, the Makefile then gives the following instructions:
Each of the points are described below:
We place ourselves in the directory in which we want to perform the installation;
It is preferable to edit file M_config before starting the initialization process so that the following variables are initialized correctly:
If your machine accepts unsatisfied references, it is not necessary to compile zzzz_mod and, in this case, ZZZZ is initialized to an empty string of characters ( ZZZZ =);
If you decide to link all the executables contained in library ppal, make sure that you have enough disk space (approximately 100 MB).
Make: Expanded macro line is too long. Stop. *** Exit 1 Stop. *** Exit 1 Stop.For further details, consult the appendix D.2.2
%.f%.o:is correct and TYPEMAKE is set to
makeMakefile. If not, (an error message will appear during the library compilation) set this variable to
In this case, the makefile tells you that you have to find the command
that allows to make this translation and to set MAJMIN in the
In order to find this command you can use these 2 files:
$racine/make/test_majcontains uppercase letters
$racine/make/test_mincontains the same lowercase letters
Note : If you modify the values of certain variables, these values should not be put between quotes, as that could result in errors at a later stage.
The value of MAJMIN has to be put between quotes.
Once file M_config has been consulted, the installation can be performed:
We are now in the second part of the Makefile, called the installation.
It is during this step that the installation is really performed (compiling, creating the executables, ...).
We remain in the installation directory throughout this step:
$MR/make/Install name of machine
During this phase the Makefile will be interrupted at least once. This interruption allows you to select the graphic peripherals. This choice is made in file periphin.in; the graphic peripherals x11 and postscript (see Appendix F) are selected by default. Thus:
# INSEREZ LA LISTE DES PERIPHERIQUES : (ne pas mettre le caractere diese en debut de ligne)
replace x11 and postscript by the graphic peripherals you wish to use (check that the value of variable STDLIB is compatible with your peripheral choice).
Having made the necessary modifications, You can now start the installation process by entering the make command.
The Makefile now continues by performing the following tasks:
To this end, a new Makefile is created in each source library, which compiles the library and stores the object files in an archive. If this target is executed several times, the Makefile will verify all the dependencies and will not do anything if everything is up-to-date, or recompile only those which are not up-to-date.
Each Makefile generated in the source libraries can easily be re-used if you install on different machines without duplicating the source code.
Any error messages generated during compilation are written on file:
During compilation, a directory with the name of the library compiled is created in the current directory, $MR/make/Install$MM. This directory contains the object files temporarily before they are stored in a library.
If an interruption occurs during compilation, those files that are already compiled will not be lost. In fact, when the Makefile is re-started it checks, for each library, if a directory with the same name does not exist in the current directory ( $MR/make/Install$MM). If this is indeed the case, it will archive the objects contained in the directory before compiling.
As before (target libraries), we generate the Makefiles, giving the inter-dependence between the object libraries and the main programs contained in libraries test and ppal. In this manner, the link is done only with those libraries that are necessary (thus being faster).
While executing this target, several actions are performed: