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