next up previous contents index
Next: Usage Up: Getting started Previous: Developers   Contents   Index

Configuring and building

If GmkPack has already been installed by an administrator, you can skip this section.

Before using GmkPack , you have to ''configure'' it and ''build'' it. Because GmkPack has been written in a very primitive way, this configuration step consists just in filling properly the configuration file (GMKFILE) so that the building process can run.
The building process does very few things actually : it is a shell script which checks some environment variables, checks some variables from the configuration file and sets the files permissions ; then it might build a program (for distributed compilation) and finally it installs the man pages. All that is very fast to run.
The building process can abort if the configuration file does not fit. However all that is in the configuration file is not needed at the time of the building process, so that you can finalize the configuration file much later after you have build GmkPack . However, it is better to start with a proper configuration file !

*
Your Shell should be ksh or bash. Other Shell may work but they have not been tested. You need Perl, too, and at least perl 5.0 version 6 subversion 1 ; perl 5.0 patchlevel 4 subversion 4 has been proven not to be a sufficient version.
*
Change to the directory where GmkPack is installed and invoke build_gmkpack ; the standard output should look so :
Environment variables :
SHELL=/bin/bash
PERL=/usr/bin/perl
GMKFILE=PGI.LXGMAP
Directories/files permissions :
Overview of architecture file :
GMKWRKDIR=/home/khatib/tmp/gmktmp.12895
LIBFRT=PGI616
Install codes configuration files :
Install scripts :
aux/bl95stuffpack.sh ...
aux/catenvpack.sh ...
aux/cplpack.sh ...
aux/create_odbglue.sh ...
aux/depspack.sh ...
aux/dummylibspack.sh ...
aux/envvarpack.sh ...
aux/ggetpack.sh ...
aux/icspack.sh ...
aux/intfbF90.sh ...
aux/libspack.sh ...
aux/licensepack.sh ...
aux/lnkpack.sh ...
aux/loadpack.sh ...
aux/mkcplpack.sh ...
aux/mkdirpack.sh ...
aux/mkintfb.sh ...
aux/noupdpack.sh ...
aux/odbstuffpack.sh ...
aux/pathpack.sh ...
aux/Pcplpack.sh ...
aux/privarpack.sh ...
aux/Psystem.sh ...
aux/Pupdpack.sh ...
aux/Pviewpack.sh ...
aux/sizepack.sh ...
aux/sortpack.sh ...
aux/splitpack.sh ...
aux/syspack.sh ...
aux/unsxrpack.sh ...
aux/updpack.sh ...
aux/viewpack.sh ...
aux/vppstuffpack.sh ...
aux/wrkpack.sh ...
aux/gmak.pl ...
aux/lib-file.pl ...
aux/lib-shell.pl ...
aux/make_intfbl.pl ...
aux/my_check_inc_intfb.pl ...
aux/my_check_norm.pl ...
aux/sun_specific.pl ...
util/admpack ...
util/clearpack ...
util/envpack ...
util/flushpack ...
util/genpack ...
util/gmkpack ...
util/idotpack ...
util/lockpack ...
util/logpack ...
util/lspack ...
util/progpack ...
util/Psize ...
util/readpack ...
util/resetpack ...
util/rlspack ...
util/rmpack ...
util/scanpack ...
util/showpack ...
util/usrpack ...
util/vipack ...
spl/mpsh.pl ...
Install man pages :
Installation finished for SERIAL execution (Maximum number of threads on this machine : 1).
*
If the procedure stops before the installation is finished, then you should fix your configuration file.
*
Once the installation is successful, you can run the command envpack which will print out some information about your environment related to GmkPack :
GMKROOT  = /home/khatib/bin/gmkpack.6.3
ROOTPACK = /home/khatib/rootpack
HOMEPACK = /home/khatib/pack
HOMEBIN  = /home/khatib/pack
GMKTMP   = /home/khatib/tmp
gmkpack is /home/khatib/bin/gmkpack.6.3/util/gmkpack
registered as : /home/khatib/bin/gmkpack.6.3/util/gmkpack
*
To make the maintenance and upgrade of GmkPack transparent to the developers, the administrator is invited to create a symbolic link from gmkpack to the last version installed :
% cd $(dirname $GMKROOT)
% ln -s $(basename $GMKROOT) gmkpack


next up previous contents index
Next: Usage Up: Getting started Previous: Developers   Contents   Index
EL KHATIB Ryad 2008-05-23