qmake-ge (1) Linux Manual Page
qmake – distributed parallel make, scheduling by Grid Engine.
Syntax
qmake [ options ] — [ gmake options ]Description
Qmake is a parallel, distributed utility. Scheduling of the parallel make tasks is done by Grid Engine. It is based on gmake (GNU make), version 3.78.1. Both Grid Engine and gmake command line options can be specified. They are separated by "–".All Grid Engine options valid with or can be specified with qmake – see for a description of all Grid Engine command line options. The manual page describes the gmake command line syntax.
The syntax of qmake makefiles corresponds to gmake and is described in the "GNU Make Manual".
A typical qmake call will use the Grid Engine command line options -cwd to have a scheduled make started in the current working directory on the execution host, -v PATH if the Grid Engine environment is not setup in the users .cshrc or .profile shell resource file and request slots in a parallel environment (see ).
If no resource request (Grid Engine command line option -l) is specified, qmake will use the environment variable SGE_ARCH to request the same architecture for task execution as has the submit host. If SGE_ARCH is set, the architecture specified in SGE_ARCH will be requested by inserting the option -l arch=$SGE_ARCH into the command line options. If SGE_ARCH is not set, the make tasks can be executed on any available architecture. As this is critical for typical make (compile) jobs, a warning will be output.
qmake has two different modes for allocating Grid Engine resources for the parallel execution of tasks:
1. Allocation of resources using a parallel environment. If the -pe option is used on the qmake command line, a parallel job is scheduled by Grid Engine. The make rules are executed as tasks within this parallel job.
2. Dynamic allocation of resources. If no parallel environment is requested when submitting a qmake job, each make rule will generate an individual Grid Engine qrsh job. All resource requests given to qmake will be inherited by the jobs processing the make rules.
In dynamic allocation mode, additional resource requests for individual rules can be specified by preceding the rule by the definition of an environment variable SGE_RREQ. The rule then takes the form SGE_RREQ="<request>" <rule>, e.g. SGE_RREQ="-l lic=1" cc -c … If such makefile rules are executed in a make utility other than qmake, the environment variable SGE_RREQ will be set in the environment established for the rule’s execution – without any effect.
Examples
- qmake -cwd -v PATH -pe compiling 1-10 —
- qmake -l arch=sol-sparc -cwd -v PATH — -j 4
If the following Makefile is submitted with the above command line, additional resource requests will be made for individual rules: For the compile and link rules, compiler licenses (comp) and linker licenses (link) will be requested, in addition to the resource request made for the whole job (-l arch=sol-sparc) on the command line.
- all: test
clean:
rm -f test main.o functions.o
test: main.o functions.o
SGE_RREQ="-l link=1" ld -o test main.o functions.o
main.o: main.c
SGE_RREQ="-l comp=1" cc -c -DALIASPATH=
functions.o: functions.c
SGE_RREQ="-l comp=1" cc -c -DALIASPATH=
- qmake -cwd -v PATH -l arch=sol-sparc64 -pe make 3 —
The shell script
- #!/bin/sh
qmake -inherit —
- qsub -cwd -v PATH -pe make 1-10 [further ge options] <script>
Environmental Variables
- GE_ROOT
- Specifies the location of the Grid Engine standard configuration files.
- GE_CELL
- If set, specifies the default Grid Engine cell. To address a Grid Engine cell qmake uses (in the order of precedence):
- The name of the cell specified in the environment variable GE_CELL, if it is set.
The name of the default cell, i.e. default.
- The name of the cell specified in the environment variable GE_CELL, if it is set.
- GE_DEBUG_LEVEL
- If set, specifies that debug information should be written to stderr. In addition the level of detail in which debug information is generated is defined.
- SGE_ARCH
- The architecture of the submit host. If this variable is set in the submission environment, qmake will request the given architecture for job execution (see DESCRIPTION above).
Known Problems
Slow NFS server
Very low file server performance may lead to problems on depending files. Example: Host a compiles a.c to a.o, host b compiles b.c to b.o, host c shall link program c from a.o and b.o. In case of very bad NFS performance, host c might not yet see files a.o and b.o.
Multiple commands in one rule
If multiple commands are executed in one rule, the makefile has to ensure that they are handled as one command line.Example:
- libx.a:
- cd x
ar ru libx.a x.o
- cd x
- libx.a:
- cd x ; ar ru libx.a x.o
- cd x ; ar ru libx.a x.o
- libx.a:
- cd x ; \
ar ru libx.a x.o
- cd x ; \
See Also
, as well as (GNU make manpage) and The GNU Make Manual in <ge_root>/3rd_party/qmake.Copyright
Qmake contains portions of Gnu Make (gmake), which is the copyright of the Free Software Foundation, Inc., Boston, MA, and is protected by the Gnu General Public License.See and the information provided in <ge_root>/3rd_party/qmake for a statement of further rights and permissions.
