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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2019.2 (Released June 5, 2019) -->
<HTML lang="EN">
<HEAD>
<TITLE>2.3 configure</TITLE>
<META NAME="description" CONTENT="2.3 configure">
<META NAME="keywords" CONTENT="user_guide">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="viewport" CONTENT="width=device-width, initial-scale=1.0">
<META NAME="Generator" CONTENT="LaTeX2HTML v2019.2">
<LINK REL="STYLESHEET" HREF="user_guide.css">
<LINK REL="next" HREF="node11.html">
<LINK REL="previous" HREF="node9.html">
<LINK REL="next" HREF="node11.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A
HREF="node11.html">
<IMG WIDTH="37" HEIGHT="24" ALT="next" SRC="next.png"></A>
<A
HREF="node7.html">
<IMG WIDTH="26" HEIGHT="24" ALT="up" SRC="up.png"></A>
<A
HREF="node9.html">
<IMG WIDTH="63" HEIGHT="24" ALT="previous" SRC="prev.png"></A>
<A ID="tex2html162"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALT="contents" SRC="contents.png"></A>
<BR>
<B> Next:</B> <A
HREF="node11.html">2.4 Libraries</A>
<B> Up:</B> <A
HREF="node7.html">2 Installation</A>
<B> Previous:</B> <A
HREF="node9.html">2.2 Prerequisites</A>
<B> <A ID="tex2html163"
HREF="node1.html">Contents</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A ID="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A ID="tex2html164"
HREF="node10.html#SECTION00033100000000000000">2.3.1 Manual configuration</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H2><A ID="SECTION00033000000000000000">
2.3 <TT>configure</TT></A>
</H2>
<P>
To install the Q<SMALL>UANTUM </SMALL>ESPRESSO source package, run the <TT>configure</TT> script. This is actually a wrapper to the true <TT>configure</TT>,
located in the <TT>install/</TT> subdirectory (<TT>configure</TT> -h for help).
<TT>configure</TT> will (try to) detect compilers and libraries available on
your machine, and set up things accordingly. Presently it is expected
to work on all "common" computers, that is: based on Intel, AMD, ARM
CPUs, running Linux, Mac OS X, MS-Windows. Q<SMALL>UANTUM </SMALL>ESPRESSO is known go work on many
more kinds of machines but may requires some tweaking, especially for
the hardware of large HPC centers. Detailed but sometimes outdated
installation instructions for specific HPC machines may be found in
files <TT>install/README.</TT><EM>sys</EM>, where <EM>sys</EM> is the machine name.
<P>
Note: support for CMake is being added.
<P>
Instructions for the impatient:
<PRE>
cd qe-X.Y.Z/
./configure
make all
</PRE>
This will (try to) produce parallel (MPI) executable if a proper parallel
environment is detected, serial executables otherwise. For OpenMP executables,
specify <TT>./configure –enable-openmp</TT>. Symlinks to executable programs
will be placed in the <TT>bin/</TT>
subdirectory. Note that both C and Fortran compilers must be in your execution
path, as specified in the PATH environment variable.
<P>
<TT>configure</TT> generates the following files:
<P>
<TABLE CELLPADDING=3>
<TR><TD ALIGN="LEFT"><TT>make.inc</TT></TD>
<TD ALIGN="LEFT">compilation rules and flags (used by <TT>Makefile</TT>)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>install/configure.msg</TT></TD>
<TD ALIGN="LEFT">a report of the configuration run (not needed for compilation)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>install/config.log</TT></TD>
<TD ALIGN="LEFT">detailed log of the configuration run (useful for debugging)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>include/qe_cdefs.h</TT></TD>
<TD ALIGN="LEFT">(previously: <TT>include/c_defs.h</TT>)
a few definitions used by C files</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>include/configure.h</TT></TD>
<TD ALIGN="LEFT">optionally: info on compilation flags
(uncomment <code>#define __HAVE_CONFIG_INFO</code>
in Modules/environment.f90 to enable its usage)</TD>
</TR>
</TABLE>
<BR>
NOTA BENE: if you interrupt <TT>make</TT>, it may fail when you start it again
later (this will happen for instance if <TT>make</TT> is interrupted while unpacking
and compiling the FoX library). If so, run <TT>make clean</TT> before
running <TT>make</TT> again.
<BR>
NOTA BENE 1: it is convenient to use "parallel <TT>make</TT>" to speed up compilation:
<TT>make -jN</TT> compiles in parallel on N processors.
<BR>
NOTA BENE 2: <TT>configure</TT> no longer updates files <TT>make.depend</TT>,
containing dependencies upon modules, in the various subdirectories.
If you modify the sources, run <TT>./install/makedeps.sh</TT> or type
<TT>make depend</TT> to update files <TT>make.depend</TT>.
<BR>
NOTA BENE 3: <TT>make.inc</TT> used to be called <TT>make.sys</TT>
until v.6.0. The change of name is due to frequent problems with mailers
assuming that whatever ends in <TT>.sys</TT> is a suspect virus.
<P>
You should always be able to compile the Q<SMALL>UANTUM </SMALL>ESPRESSO suite
of programs without having to edit any of the generated files. However you
may have to tune <TT>configure</TT> by specifying appropriate environment variables
and/or command-line options. Usually the tricky part is to get external
libraries recognized and used: see Sec.<A HREF="node11.html#Sec:Libraries">2.4</A>
for details and hints.
<P>
Environment variables may be set in any of these ways:
<PRE>
export VARIABLE=value; ./configure # sh, bash, ksh
setenv VARIABLE value; ./configure # csh, tcsh
env VARIABLE=value ./configure # any shell
./configure VARIABLE=value # any shell
</PRE>
As a rule: do not define environment variables for <TT>configure</TT> unless
you need it. Always try <TT>configure</TT> with no options as a first step.
Some environment variables that are relevant to <TT>configure</TT> are:
<P>
<TABLE CELLPADDING=3>
<TR><TD ALIGN="LEFT"><TT>ARCH</TT></TD>
<TD ALIGN="LEFT">label identifying the machine type (see below)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>F90, F77, CC</TT></TD>
<TD ALIGN="LEFT">names of Fortran, Fortran-77, and C compilers</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>MPIF90</TT></TD>
<TD ALIGN="LEFT">name of parallel Fortran 90 compiler (using MPI)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>CPP</TT></TD>
<TD ALIGN="LEFT">source file preprocessor (defaults to $CC -E)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>LD</TT></TD>
<TD ALIGN="LEFT">linker (defaults to $MPIF90)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>(C,F,F90,CPP,LD)FLAGS</TT></TD>
<TD ALIGN="LEFT">compilation/preprocessor/loader flags</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>LIBDIRS</TT></TD>
<TD ALIGN="LEFT">extra directories where to search for libraries</TD>
</TR>
</TABLE>
<BR>(note that <TT>F90</TT> is an ``historical'' name – we actually use
Fortran 2003 – and that it should be used only together with option
<TT>–disable-parallel</TT>. In fact, the value of F90 must be
consistent with the parallel Fortran compiler which is determined by
<TT>configure</TT> and stored in the <TT>MPIF90</TT> variable).
<P>
For example, the following command line:
<PRE>
./configure MPIF90=mpif90 FFLAGS="-O2 -assume byterecl" \
CC=gcc CFLAGS=-O3 LDFLAGS=-static
</PRE>
instructs <TT>configure</TT> to use <TT>mpif90</TT> as Fortran compiler
with flags <TT>-O2 -assume byterecl</TT>, <TT>gcc</TT> as C compiler with
flags <TT>-O3</TT>, and to link with flag <TT>-static</TT>.
Note that the value of <TT>FFLAGS</TT> must be quoted, because it contains
spaces. NOTA BENE: passing the complete path to compilers (e.g.,
<TT>F90=/path/to/f90xyz</TT>) may lead to obscure errors during
compilation.
<P>
If your machine type is unknown to <TT>configure</TT>, you may use the
<TT>ARCH</TT>
variable to suggest an architecture among supported ones. Some large
parallel machines using a front-end (e.g. Cray XT) will actually
need it, or else <TT>configure</TT> will correctly recognize the front-end
but not the specialized compilation environment of those machines.
In some cases, cross-compilation requires to specify the target machine with the
<TT>–host</TT> option. This feature has not been extensively
tested, but we had at least one successful report (compilation
for NEC SX6 on a PC). Currently supported architectures are:
<P>
<TABLE CELLPADDING=3>
<TR><TD ALIGN="LEFT"><TT>x86_64</TT></TD>
<TD ALIGN="LEFT">Intel and AMD 64-bit running Linux</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>arm</TT></TD>
<TD ALIGN="LEFT">ARM machines (with gfortran or armflang)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>crayxt4</TT></TD>
<TD ALIGN="LEFT">Cray XT4/XT5/XE machines</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>mac686</TT></TD>
<TD ALIGN="LEFT">Apple Intel machines running Mac OS X</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>mingw32</TT></TD>
<TD ALIGN="LEFT">Cross-compilation for MS-Windows, using mingw, 32 bits</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>mingw64</TT></TD>
<TD ALIGN="LEFT">As above, 64 bits</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>cygwin</TT></TD>
<TD ALIGN="LEFT">MS-Windows PCs with Cygwin</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>ppc64</TT></TD>
<TD ALIGN="LEFT">Linux PowerPC machines, 64 bits</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>ppc64-mn</TT></TD>
<TD ALIGN="LEFT">as above, with IBM xlf compiler</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>ppc64-bg*</TT></TD>
<TD ALIGN="LEFT">IBM BlueGene</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>necsx*</TT></TD>
<TD ALIGN="LEFT">NEC SX-6 and SX-8 machines</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>ia32*</TT></TD>
<TD ALIGN="LEFT">Intel 32-bit machines (x86) running Linux</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>ia64*</TT></TD>
<TD ALIGN="LEFT">Intel 64-bit (Itanium) running Linux</TD>
</TR>
</TABLE>
<BR>
<P>
<EM>Note</EM>: <TT>x86_64</TT> replaces <TT>amd64</TT> since v.4.1.
Cray Unicos machines, SGI machines with MIPS architecture, HP-Compaq Alphas
are no longer supported since v.4.2; PowerPC Macs are no longer
supported since v.5.0; IBM machines with AIX are no longer supported
since v.6.0. Architectures marked with a * are to be considered obsolescent
or obsolete.
<P>
Finally, <TT>configure</TT> recognizes the following command-line options:
<BR><TABLE CELLPADDING=3>
<TR><TD ALIGN="LEFT"><TT>–enable-parallel</TT></TD>
<TD ALIGN="LEFT">compile for parallel (MPI) execution if possible (default: yes)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–enable-openmp</TT></TD>
<TD ALIGN="LEFT">compile for OpenMP execution if possible (default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–enable-shared</TT></TD>
<TD ALIGN="LEFT">use shared libraries if available (default: yes;</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">"no" is implemented, untested, in only a few cases)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–enable-debug</TT></TD>
<TD ALIGN="LEFT">compile with debug flags (only for some compilers; default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–enable-pedantic</TT></TD>
<TD ALIGN="LEFT">compile with pedantic flags (only for gfortran; default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–enable-signals</TT></TD>
<TD ALIGN="LEFT">enable signal trapping (default: disabled)</TD>
</TR>
</TABLE>
<BR>
<BR>
and the following optional packages:
<BR><TABLE CELLPADDING=3>
<TR><TD ALIGN="LEFT"><TT>–with-scalapack</TT></TD>
<TD ALIGN="LEFT">(yes|no|intel) Use scalapack if available.</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">Set to <TT>intel</TT> to use Intel MPI and blacs (default: use OpenMPI)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-elpa-include</TT></TD>
<TD ALIGN="LEFT">Specify full path of ELPA include and modules
headers (default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-elpa-lib</TT></TD>
<TD ALIGN="LEFT">Specify full path of the ELPA library
(default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-elpa-version</TT></TD>
<TD ALIGN="LEFT">Specify ELPA version, only year (2015 or 2016,
default: 2016)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-hdf5</TT></TD>
<TD ALIGN="LEFT">(no | | yes | <TT><path></TT>)</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">Use HDF5, if yes configure assumes</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">that a valid installation with version >= 1.8.16 is</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">available, and h5cc and h5fc are in the default</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">executable search path; <path> must be the root</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">folder of a standalone hdf5 installation. (default: no).</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-hdf5-libs=</TT></TD>
<TD ALIGN="LEFT">Specify the linker options needed by HDF5 when</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">configure fails to detect them by itself. As value</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">to specify here is usually composed by many</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">substrings it should be enclosed by quotes so to</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">prevent configure failures. (default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-hdf5-include</TT></TD>
<TD ALIGN="LEFT">Specify full path the HDF5 include folder containing</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">module and headers files. Use it if configure fails</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">to detect the path by itself. (default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-libxc</TT></TD>
<TD ALIGN="LEFT">Link the <TT>libxc</TT> library (default:no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-libxc-prefix</TT></TD>
<TD ALIGN="LEFT">directory where <TT>libxc</TT> is installed</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-libxc-include</TT></TD>
<TD ALIGN="LEFT">directory where <TT>libxc</TT> Fortran headers reside</TD>
</TR>
</TABLE>
<BR>
<BR>
The following options are available for the CUDA Fortran GPU version:
<BR><TABLE CELLPADDING=3>
<TR><TD ALIGN="LEFT"><TT>–with-cuda=value</TT></TD>
<TD ALIGN="LEFT">enables compilation of the CUDA Fortran</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">accelerated subroutines.</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT"><TT>value</TT> should point the path where the CUDA toolkit</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">is installed, e.g. <TT>/opt/cuda</TT> (default: no)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-cuda-cc=value</TT></TD>
<TD ALIGN="LEFT">sets the compute capabilities for the compilation</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">of the accelerated subroutines.</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT"><TT>value</TT> must be consistent with the hardware and the</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">NVidia driver installed on the workstation or on the</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">compute nodes of the HPC facility (default: 35)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–with-cuda-runtime=value</TT></TD>
<TD ALIGN="LEFT">sets the version of the CUDA toolkit used</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">for the compilation of the accelerated code.</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT"><TT>value</TT> must be consistent with the</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">CUDA Toolkit installed on the workstation</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">or available on the compute nodes of the HPC facility.</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">PGI compilers currently accept 7.5, 8.0 or 9.0 (default: 8.0)</TD>
</TR>
<TR><TD ALIGN="LEFT"><TT>–enable-cuda-env-check=[yes]</TT></TD>
<TD ALIGN="LEFT">if set, sanity checks on the CUDA environment</TD>
</TR>
<TR><TD ALIGN="LEFT"> </TD>
<TD ALIGN="LEFT">are performed (default: yes).</TD>
</TR>
</TABLE>
<BR>
<P>
Please remember that in order to compile the CUDA code for GPU's you need ...
the CUDA code (it is aligned to but separated from the main distribution)!
you also need a recent version of the PGI Fortran compiler.
OpenMP must be enabled,
and you may want to use a CUDA-aware MPI distribution to optimize the data
transfer between the processes.
<P>
If you want to modify <TT>configure</TT> (advanced users only!),
see the Wiki pages on GitLab.
<P>
<H3><A ID="SECTION00033100000000000000"></A>
<A ID="SubSec:manconf"></A>
<BR>
2.3.1 Manual configuration
</H3>
If <TT>configure</TT> stops before the end, and you don't find a way to fix
it, you have to write a working <TT>make.inc</TT> file (optionally,
<TT>include/qe_cdefs.h</TT>). The template used by <TT>configure</TT> is
<TT>install/make.inc.in</TT> and contains explanations of the meaning
of the various variables. Note that you may need
to select appropriate preprocessing flags
in conjunction with the desired or available
libraries (e.g. you need to add <TT>-D__FFTW</TT> to <TT>DFLAGS</TT>
if you want to link internal FFTW). For a correct choice of preprocessing
flags, refer to the documentation in <TT>include/defs.h.README</TT>.
<P>
NOTA BENE: If you change any settings (e.g. preprocessing,
compilation flags)
after a previous (successful or failed) compilation, you must run
<TT>make clean</TT> before recompiling, unless you know exactly which
routines are affected by the changed settings and how to force their
recompilation. <TT>configure</TT> will clean objects and executables, unless
you use option <TT>–save</TT>.
<P>
<HR>
<!--Navigation Panel-->
<A
HREF="node11.html">
<IMG WIDTH="37" HEIGHT="24" ALT="next" SRC="next.png"></A>
<A
HREF="node7.html">
<IMG WIDTH="26" HEIGHT="24" ALT="up" SRC="up.png"></A>
<A
HREF="node9.html">
<IMG WIDTH="63" HEIGHT="24" ALT="previous" SRC="prev.png"></A>
<A ID="tex2html162"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALT="contents" SRC="contents.png"></A>
<BR>
<B> Next:</B> <A
HREF="node11.html">2.4 Libraries</A>
<B> Up:</B> <A
HREF="node7.html">2 Installation</A>
<B> Previous:</B> <A
HREF="node9.html">2.2 Prerequisites</A>
<B> <A ID="tex2html163"
HREF="node1.html">Contents</A></B>
<!--End of Navigation Panel-->
</BODY>
</HTML>
|
