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
|
Installation Instructions for PSI3
----------------------------------
I. Compilation Prerequisites
II. Brief Summary of Configruation, Compilation, and Installation
III. Detailed Installation Instructions
IV. Recommendations for BLAS and LAPACK libraries
V. Miscellaneous architecture-specific notes
----------------------------------
I. Compilation Prerequisites:
* ANSI C compiler
* C++ Compiler
* F77 Compiler (the F95 compiler, gfortran, with gcc-4.X will work)
--> Note: The F77 compiler is only used to determine the symbol-naming
convention of and some system routines for the BLAS and LAPACK libraries
on a few architectures. It is optional in a few cases (e.g. Mac OS X
systems).
* Optimized BLAS library (see recommendations below)
* Optimized LAPACK library (see recommendations below)
* POSIX threads (Pthreads) library (optional)
* Perl interpreter (5.005 or higher; needed for running test cases)
* GNU utilities: (see http://www.gnu.org)
** make
** flex
** bison
** autoconf (version 2.52 or higher)
** fileutils (esp. install)
* For documentation:
** latex
** latex2html
(for generating web-based documentation only; either v0.99_1 or
1.62, but you must apply the patch supplied in psi3/misc)
II. Brief Summary of Configruation, Compilation, and Installation
A good directory for the PSI3 source code is /usr/local/src/psi3.
The directory should NOT be named /usr/local/psi, as that is the default
installation directory unless changed by the --prefix directive (see below).
It should also not have any periods in the path, e.g., /usr/local/psi3.2,
because of a bug in dvips which will cause the compilation of documentation
to fail.
The following series of steps will configure and build the PSI3 package
and install the executables in /usr/local/psi/bin:
* cd $PSI3 (the top-level PSI3 source directory -- probably THIS directory)
* mkdir objdir
* cd objdir
* ../configure
* make
* make tests (optional, but recommended)
* make install
* make doc (optional)
You may need to make use of one or more of the following options to
the configure script:
* --prefix=directory --- Use this option if you wish to install the
PSI3 package somewhere other than the default directory, /usr/local/psi.
* --with-cc=compiler --- Use this option to specify a C compiler.
One should use compilers that generate reentrant code, if possible. The
default search order for compilers is: cc_r (AIX only), gcc, icc, cc.
* --with-cxx=compiler --- Use this option to specify a C++ compiler.
One should use compilers that generate reentrant code, if possible.
The default search order for compilers is: xlC_r (AIX only), g++, c++,
icpc, cxx.
* --with-fc=compiler --- Use this option to specify a Fortran-77 compiler,
which is used to determine linking coventions for BLAS and LAPACK libraries
and to provide system routines for those libraries. Note that no fortran
compiler is necessary on Mac OS X systems (see below). The default search
order for compilers is: xlf_r (AIX only), gfortran, g77, ifort, f77, f2c.
* --with-f77symbol=value --- This option allows manual assignment of the
FORTRAN77 symbol convention, which is necessary for C programs to link
Fortran-interface libraries such as BLAS and LAPACK. This option should
only be used by experts and even then should almost never be necessary.
Allowed values are:
lc : lower-case
lcu : lower-case with underscore (default)
uc : upper-case
ucu : upper-case with underscore
* --with-ld=linker --- Use this option to specify a linker. The
default is 'ld'.
* --with-ar=archiver --- Use this option to specify an archiver. The
default is to look for 'ar' automatically.
* --with-ar-flags=flags --- Use this option to specify additional archiver
flags. The default is 'r'.
* --with-incdirs=directories --- Use this option to specify extra
directories where to look for header files. Directories should be specified
prepended by '-I', i.e. '-Idir1 -Idir2', etc. If several directories are
specified, enclose the list with single right-quotes, e.g.,
--with-incdirs='-I/usr/local/include -I/home/psi3/include'.
* --with-libs=libraries --- Use this option to specify extra
libraries which should be used during linking. Libraries should be
specified by their full names or in the usual '-l' notation, e.g.
'-lm /usr/lib/libm.a', etc. If several libraries are specified, enclose
the list with single right-quotes, e.g., --with-libs='-libm -lgcc_s'.
* --with-libdirs=directories --- Use this option to specify extra
directories where to look for libraries. Directories should be specified
prepended by '-L', i.e. '-Ldir1 -Ldir2', etc. If several directories are
specified, enclose the list with single right-quotes, e.g.,
--with-libdirs='-L/usr/local/lib -I/home/psi3/lib'.
* --with-blas=library --- Use this option to specify a BLAS library.
If your BLAS library has multiple components, enclose the file list
with single right-quotes, e.g., --with-blas='-lf77blas -latlas'. Note
that many BLAS libraries can be detected automatically.
* --with-lapack=library --- Use this option to specify a LAPACK library.
If your LAPACK library has multiple components, enclose the file list
with single right-quotes, e.g., --with-lapack='-llapack -lcblas -latlas'.
Note that many LAPACK libraries can be detected automatically.
* --with-max-am-eri=integer --- Specifies the maximum angular momentum
level for the primitive Gaussian basis functions when computing
electron repulsion integrals. This is set to g-type functions (AM=4)
by default.
* --with-max-am-deriv1=integer --- Specifies the maximum angular
momentum level for first derivatives of the primitive Gaussian
basis functions. This is set to f-type functions (AM=3) by default.
* --with-max-am-deriv2=integer --- Specifies the maximum angular
momentum level for second derivatives of the primitive Gaussian
basis functions. This is set to d-type functions (AM=2) by default.
* --with-max-am-r12=integer --- Specifies the maximum angular momentum
level for primitive Gaussian basis functions used in r_12 explicitly
correlated methods. This is set to f-type functions (AM=3) by default.
* --with-debug=yes/no --- Turns on debugging flags (-g) if yes. This is
set to no by default.
* --with-opt=yes/no --- Turns off compiler optimizations (-OX) if no.
This is set to yes by default.
* --with-strict=yes -- Turns on strict compiler warnings.
III. Detailed Installation Instructions
This section provides a more detailed explanation of the procedure for
compiling and installing the PSI3 package.
III.A. Step 1: Configuration
First, we recommend that you choose for the top-level $PSI3 source
directory something other than /usr/local/psi; your $HOME directory or
/usr/local/src/psi3 are convenient choices. Next, in the top-level $PSI3
source directory you've chosen, first run autoconf to generate the configure
script from configure.ac. It is best to keep the source code separate
from the compilation area, so you must first choose a subdirectory for
compilation of the codes. A simple option is $PSI3/objdir, which should
work for most environments. However, if you need executables for several
architectures, you should choose more meaningful subdirectory names.
* The compilation directory will be referred to as $objdir for the
remainder of these instructions.
In $objdir, run the configure script found in the $PSI3 top-level source
directory. This script will scan your system to locate certain libraries,
header files, etc. needed for complete compilation. The script accepts a
number of options, all of which are listed above. The most important of
these is the --prefix option, which selects the installation directory for
the executables, the libraries, header files, basis set data, and other
administrative files. The default --prefix is /usr/local/psi.
* The configure script's --prefix directory will be referred to as
$prefix for the remainder of these instructions.
III.B. Step 2: Compilation
Running "make" (which must be GNU's 'make' utility) in $objdir will compile
the PSI3 libraries and executable modules.
III.C. Step 3: Testing
To execute automatically the ever-growing number of test cases after
compilation, simply execute "make tests" in the $objdir directory.
This will run each (relatively small) test case and report the results.
Failure of any of the test cases should be reported to the developers.
By default, any such failure will stop the testing process. If you desire
to run the entire testing suit without interruption, execute "make tests
TESTFLAGS='-u -q'". Note that you must do a "make testsclean" in $objdir
to run the test suite again.
III.D. Step 4: Installation
Once testing is complete, installation into $prefix is accomplished by
running "make install" in $objdir. Executable modules are installed in
$prefix/bin, libraries in $prefix/lib, and basis set data and other control
strctures $prefix/share.
III.E. Step 5: Building Documentation
If your system has the appropriate utilities, you may build the
package documentation from the top-level $objdir by running "make doc".
The resulting files will appear in the $prefix/doc area.
III.F. Step 6: Cleaning
All object files and libraries can be removed to save disk space by running
"make clean" in $objdir.
III.G. Step 7: User Configuration
After the PSI3 package has been successfullly installed, the user will need
to add the installation directory into his/her path. If the package has
been installed in the default location /usr/local/psi, then in C shell,
the user should add something like the following to their .cshrc file:
setenv PSI /usr/local/psi
set path = ($path $PSI/bin)
setenv MANPATH $PSI/doc/man:$MANPATH
The final line will enable the use of the PSI3 man pages.
IV. Recommendations for BLAS and LAPACK libraries
Much of the speed and efficiency of the PSI3 programs depends on the
corresponding speed and efficiency of the available BLAS and LAPACK libraries
(especially the former). In addition, the most common compilation problems
involve these libraries. Users may therefore wish to consider the following
BLAS and LAPACK recommendations when building PSI3:
(1) It is NOT wise to use the stock BLAS library provided with many
Linux distributions like RedHat. This library is usually just the
netlib distribution and is completely unoptimized. PSI3's performance
will suffer if you choose this route. The choice of LAPACK is less
critical, and so the unoptimized netlib distribution is acceptable.
If you do choose to use the RedHat/Fedora stock BLAS and LAPACK, be
aware that some RPM's do not make the correct symbolic links.
For example, you may have /usr/lib/libblas.so.3.1.0 but not
/usr/lib/libblas.so. If this happens, create the link as, e.g.,
ln -s /usr/lib/libblas.so.3.1.0 /usr/lib/libblas.so. You
may need to do similarly for lapack.
(2) Perhaps the best choices for BLAS are Kazushige Goto's hand-optimized
BLAS (http://www.tacc.utexas.edu/resources/software/) and ATLAS
(http://math-atlas.sourceforge.net/). These work well on nearly every
achitecture to which the PSI3 developers have access, though we have
identified at least one case in which the Goto libraries yielded faulty
DGEMM calls. On Mac OS X systems, however, the vecLib package that comes
with Xcode works well. Note also that we have encountered problems with the
version 10 of Intel's MKL, particularly for very large coupled cluster
calculations.
(3) PSI3 does not require a Fortran compiler, unless the resident BLAS
and LAPACK libraries require Fortran-based system libraries. If you see
compiler complaints about missing symbols like "do_fio" or "e_wsfe", then
your libraries were most likely compiled with g77 or gfortran, which
require -lg2c to resolve the Fortran I/O calls. Use of the same gcc
package for PSI3 should normally resolve this problem.
(4) The PSI3 configure script can often identify and use several
different BLAS and LAPACK libraries, but its ability to do this
automatically depends on a number of factors, including correspondence
between the compiler used for PSI3 and the compiler used to build
BLAS/LAPACK, placement of the libraries in commonly searched directories,
etc. PSI3's configure script will find your BLAS and LAPACK if any of the
the following are installed in standard locations (e.g. /usr/local/lib):
(a) ATLAS: libf77blas.a and libatlas.a, plus netlib's liblapack.a
(b) MKL 8: libmkl.so and libmkl_lapack64.a (with the corresponding
Intel compilers)
(c) Goto: libgoto.a and netlib's liblapack.a
(d) Cray SCSL (e.g. on SGI Altix): libscs.so (NB: No Fortran compiler
is necessary in this case, so --with-fc=no should work.)
(e) ESSL (e.g. on AIX systems): libessl.a
(5) If configure cannot identify your BLAS and LAPACK libraries
automatically, you can specify them on the command-line using the
--with-blas and --with-lapack arguments described above. Here are a few
examples that work on the PSI3 developers' systems:
(a) Linux with ATLAS:
--with-blas='-lf77blas -latlas' --with-lapack='-llapack -lcblas'
(b) Mac OS X with vecLib:
--with-blas='-altivec -framework vecLib' --with-lapack=' '
(c) Linux with MKL 8.1 and icc/icpc/ifort 9.1:
--with-libdirs=-L/usr/local/opt/intel/mkl/8.0.2/lib/32 --with-blas=-lmkl --with-lapack=-lmkl_lapack32
(d) Linux on ia32 with MKL 10.1 and icc/icpc 11.0:
--with-blas='-Wl,--start-group -L/usr/local/opt/intel/mkl/10.1.0.015/lib/32 -l mkl -Wl,--end-group -lguide -lpthread'
V. Miscellaneous architecture-specific notes
* Linux on x86 and x86_64:
(1) gcc compiler: versions 3.2, 3.3, 3.4, 4.0, and 4.1 have been tested.
(2) Intel compilers: versions 9.0 and 11.0 have been tested. We do not
recommend using version 8.1.
(3) Portland Group compilers: version 6.0-5 has been tested.
(4) Some versions of RedHat/Fedora Core RPM packages for the
BLAS and LAPACK libraries fail to make all the required symlinks.
For example, you may have /usr/lib/libblas.so.3.1.0 but not
/usr/lib/libblas.so. If this happens, create the link as, e.g.,
ln -s /usr/lib/libblas.so.3.1.0 /usr/lib/libblas.so. You
may need to do something similar for LAPACK.
* Linux on Itanium2 (IA64):
(1) Intel compiler versions 9.0 and 10.0 have been tested and work.
Version 8.1 does not work.
(2) gcc compilers work.
* Mac OS 10.X:
(1) The compilation requires a developer's toolkit (Xcode) from apple.com.
Note that a fortran compiler is not needed for PSI 3.4 on Mac OS X systems.
(2) The libcompat.a library is no longer needed as of 1/24/2008.
(3) For apple systems, the latest configure script assumes that the vecLib
will be used for the optimized BLAS and LAPACK libraries, unless the
user indicates otherwise using the --with-blas and --with-lapack flags
to configure. If you encounter difficulty with configure, you may have
success explicitly indicating the vecLib using:
--with-blas='-altivec -framework vecLib' --with-lapack=' '
(4) Pre Mac OS 10.4: Certain PSI3 codes require significant stackspace for
compilation. Increase your shell's stacksize limit before running "make".
For csh, for example, this is done using "unlimit stacksize". [NB: This
limit appears to have been lifted in Mac OS 10.3.X (Panther).]
(5) Mac 10.5 users can take advantage of the ruby driver in PSI 3.4 by
including the following options on the configure command line:
--with-ruby-include="-I/System/Library/Frameworks/Ruby.framework/Headers"
--with-ruby-lib="-framework Ruby"
* AIX in a 64-bit environment:
We do not presently support the use of XL compilers on AIX systems. We
have tested gcc-4.1.1 under AIX 5.3, and we recommend use of the
configure flag: --with-aix64.
* SGI IRIX 6.x:
(1) MIPSpro C++ compilers prior to version 7.4 require a command-line flag
'-LANG:std' in order to compile PSI3 properly.
(2) Use command-line flag '-64' in order to produce 64-bit executables with
MIPSpro compilers. The following is an example of appropriate configure
options:
--with-cc='cc -64' --with-cxx='CC -64 -LANG:std' --with-fc='f77 -64'
(3) Under IRIX, configure will attempt to detect automatically and use
the optimized SGI Scientific Computing Software Library (SCSL).
* Compaq Alpha/OSF 5.1:
Default Bourne shell under Tru64 (/bin/sh) is not POSIX-compliant which
causes some PSI3 makefiles to fail. Set environmental variable BIN_SH to
xpg4.
|