summaryrefslogtreecommitdiffstats
path: root/configure.in
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2002-11-26 00:43:15 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2002-11-26 00:43:15 (GMT)
commitf5f61bf7832273bf3701002377659a4e98c404b3 (patch)
tree3cab5efd9113f3587f1bd56485e9bae8e39adbb5 /configure.in
parent8333adf8ffc1265440aefad62e0cd9ab33175bd7 (diff)
downloadhdf5-f5f61bf7832273bf3701002377659a4e98c404b3.zip
hdf5-f5f61bf7832273bf3701002377659a4e98c404b3.tar.gz
hdf5-f5f61bf7832273bf3701002377659a4e98c404b3.tar.bz2
[svn-r6138] Purpose:
Improvement Description: The fortran test code did not exit with error like C programs do. Without the appropriate exit code, make or shell could not tell the fortran test program has encountered errors. So, make continues on even when some fortran tests have failed. Solution: Consultant advised to use "CALL exit(code)" to simulate what C programs do. Though this is not standard Fortran, he has not seen it failed to work in most fortran compilers thought some of them, like intel compiler, may need to link in an extra library. Platforms tested: Tested on burrwhite (linux 2.4), eirene (linux 2.2), sol (Solaris 8, serial and mpich parallel), modi4. Did not use the standard commit test since this is a purely fortran fix.
Diffstat (limited to 'configure.in')
0 files changed, 0 insertions, 0 deletions