| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
of 'include 'mpih.f'
tested jam (mpich + gnu).
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Developers will now have to run bin/reconfigure (deprecated, will be removed
soon) or autogen.sh after checking out code.
Part of: HDFFV-9120
Tested on: jam with Fortran and C++
|
| |
| |
| |
| | |
MPI_FILE_OPEN. Kept using include "mpif.h" since it is not going to be depriciated. But 'USE mpi' will work now that the API is correct.
|
| |
| |
| |
| | |
"mpif.h"". Using the module causes problems on the Cray (hopper).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
405-408::fortran vars should be scoped
Scoped:
HAVE_SIZEOF
HAVE_C_SIZEOF
HAVE_STORAGE_SIZE
FORTRAN_DEFAULT_REALisDBLE
to where the tests are (in m4/aclocal_fc.m4)
Tested: jam (gnu)
|
| |
| |
| |
| |
| |
| |
| | |
4159:: Check if Fortran's default real is double precision. If it is and HL is being built then configure should fail due to bug HDFFV-889.
Fix:
This check should be located where HL is check for, and it is. Updated the comment to elimenate confusion.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
change include 'mpif.h' to module in tests
Solution:
changed to 'USE mpi' and moved the tests to m4/aclocal_fc.m4
Tested: jam (mpicc, mpif90)
|
| | |
|
| |
| |
| |
| |
| | |
Tested: jam (mpi, gfortran, intel)
--enable-fortran, and --enable-fortran --enable-fortran2003
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Change AC_TRY_RUN TO AC_TRY_COMPILE
Changed all the instances of AC_TRY_RUN for the Fortran and C++ tests to use
AC_COMPILE_IFELSE and moved all the tests to new files in m4 directory:
aclocal_cxx.m4 (for C++ tests)
aclocal_fc.m4 (for Fortran tests)
tested: jam
|
|
|
|
|
|
| |
libtool 2.4.2
Tested THG machines.
|
|
|
|
| |
Tested with h5committest on amani, heiwa, and jam.
|
|
and m4 to version 1.4.14. Also added m4 directory for m4 macros according to autoconf suggestion.
Tested with h5committest on amani, jam, and heiwa, and on linew.
|