File: README

package info (click to toggle)
gridengine 8.1.9%2Bdfsg-13.2
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 57,848 kB
  • sloc: ansic: 432,690; java: 87,068; cpp: 31,958; sh: 29,445; jsp: 7,757; perl: 6,336; xml: 5,828; makefile: 4,705; csh: 3,934; ruby: 2,221; tcl: 1,676; lisp: 669; yacc: 519; python: 503; lex: 361; javascript: 200
file content (93 lines) | stat: -rw-r--r-- 2,721 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
            Compiling PVM programs for Grid Engine Parallel Environment 
            -----------------------------------------------------------

Content
-------
   1) Introduction
   2) How aimk works
   3) What "make" creates

1) Introduction
---------------

The programs:
    
   start_pvm
   stop_pvm

will ususally be called from your start and stop procedure which you
defined in your Grid Engine/Grid Engine Enterprise Edition parallel
enviroment. Since PVM programs should be linked with the PVM version which
is running at your site, you must compile and link

   start_pvm.c
   stop_pvm.c

before setting up and using a Grid Engine/Grid Engine Enterprise Edition
parallel environment using PVM.

You should invoke the make procedure by calling the shell script

  aimk

in this directory.

2) How aimk works:
------------------

'aimk' first checks if the environment variables PVM_ROOT and PVM_ARCH are
set and point to a directory. Then aimk guesses on which machine type it is
running and sets the environment variable $ARCH, which has the same value as
it is used for the Grid Engine/Grid Engine Enterprise Edition binary
subdirectory (e.g. "solaris" for a Solaris 2.x system).

You can verify this setting by calling aimk with the "no make" option:

   % ./aimk -nomk

This will print the name of the $ARCH variable.

You will have to adjust aimk in most cases for your own needs.  You can
check what compiler settings are used, when aimk calls make, by checking the
sections

   "common compiler and linker settings"

at the beginning of aimk and by checking the architecture specific
sections later in aimk, e.g. "case sol-sparc:" or "case irix65:"

Aimk will then create a subdirectory for the architecture. It will invoke
make from this subdirectory. Binaries and objects are created in the $ARCH
subdirectory.

You can call aimk with command line parameters. 

   % ./aimk -help

will show all possible command line parameters. Other command line
parameters will be passed to make. This makes it possible creating only
selected targets, e.g.

  % ./aimk start_pvm

will only create "start_pvm".
 
  % ./aimk -n

will pass the "-n" flag to make (which causes make to print the commands
that would be executed, but does not execute them).
 

3) What "make" creates
----------------------

The default rule of the Makefile creates the binaries:

   start_pvm    (start PVM - only use with startpvm.sh) 
   stop_pvm     (shutdown pvm - only use with stop_pvm.sh)
   spmd         (a small sample program from the PVM distribution)


If you don't have "libgpvm3", you may delete "spmd" from the "all:" rule in
the Makefile. "Spmd" is not necessary for setting up the Grid Engine
parallel environment (PE).