- 01-Dec-2004: First release.
- The code requires a Fortran95 compiler.
- Each program tarball contains all the required code, test
datafiles, and a makefile for unix platforms. The makefile names in
each program tarball are the same, so if you explode the tarballs in
the same directory, rename them to prevent overwriting.
- All the required support code/modules are replicated in each
tarball.
- All compilation macros and rules are defined in
make.macros
and make.rules respectively. The make.macros file
contains the default compiler options for all the tested systems:
- linux using Intel (v8.0.046_pe050.1)
- linux using Lahey (v6.2c)
- linux using pgf90 (v5.2-1)
- SGI IRIX64
- Sun Solaris
- IBM AIX
Simply typing make on the command line will select the
correct platform. For linux systems, you should check the Linux_FLAGS
macro definition in the make.macros file to set the default compiler.
- If you are using the PGI compiler, you must have at least v5.2-1,
their Fortran95 compiler. However, this version of the compiler is
buggy and will most likely not compile all the source code. Fixes for
the most egregious problems are scheduled for the v5.2-2 release. Regardless, I've
given up on this compiler for now.
- If you are on an SGI, you may or may not be able to compile all the code. As far as I
can tell SGI don't have their own f95 compiler -- but you can purchase SGI ports of the
NAG f95 compiler. The SGI MIPSPro f90 compiler can handle most Fortran95 syntax,
but not all. In particular, my SGI test platform had problems with name specifications
on END INTERFACE statements but, strangely enough, only for defined operators
not generic procedures.
This page maintained by Paul van Delst
Last updated December 01, 2004