summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMuQun Yang <ymuqun@hdfgroup.org>2004-10-27 22:34:04 (GMT)
committerMuQun Yang <ymuqun@hdfgroup.org>2004-10-27 22:34:04 (GMT)
commit84745471a2f89660d8b0d48572a31982d12e05fa (patch)
tree2c56fc904d890e8f3629b350c01a6d433df78bfd
parent0db364390b48d705b2c3fb225651ba35a19a5b4d (diff)
downloadhdf5-84745471a2f89660d8b0d48572a31982d12e05fa.zip
hdf5-84745471a2f89660d8b0d48572a31982d12e05fa.tar.gz
hdf5-84745471a2f89660d8b0d48572a31982d12e05fa.tar.bz2
[svn-r9473] Purpose:
1.Support Fortran DLL for Decfortran 6.6c. 2. misc. small bug fixes. Description: 1. No HDF5 fortran DLL is provided in the recent HDF5 release because of 1) the difficulties to build fortran DLL based on C DLL. 2) the difficulties to separate fortran DLL from C DLL in hdf5 test suite. 3) DEC Fortran 6.0 was old and we don't have new DEC fortran 6.6 compiler. Solution: 0. Updating DEC Fortran 6.6A compiler to 6.6c since there was a bug in 6.6A to fail export variable within module procedure. 1. Using a C stub dll to separate fortran and C codes, previously they were mixed. 2. Using a C stub dll for test suite. 3. Carefully passing the token between export and import DLLs. 4. Now Fortran tests still failed with 1.7 branch, however, the failure is due to bugs inside HDF5 library because both static and DLL experienced the same failure. The failure occurred for routine h5premove_f. According to the failure message, it may be due to the invalid array bound. Anyway, Fortran DLL can be treated as the same as the static library for 1.7 branch with DEC visual 6.6c. Platforms tested: windows xp with DEC fortran 6.6c and VS 6.0. Misc. update: update some batch files and project file related to this change.
-rwxr-xr-xwindows/all.zipbin394487 -> 397765 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/windows/all.zip b/windows/all.zip
index 252e423..6887209 100755
--- a/windows/all.zip
+++ b/windows/all.zip
Binary files differ