Purpose:
Bug Fixes
Description:
If the system doesn't support modules, then the F9XMODFLAG would be
empty. This would cause things like '.' and '../src' to be stranded
on the compile line by themselves and the compiler would barf.
Also, there needs to be a dependence between the thyperslab_wr
program and the THDF5 module.
Solution:
Put the code to generate the -{M,I,p}<directory> flags in the
acsite.m4 file since it's not possible to check if a macro is empty
and do substitution on it in the Makefiles.
Put a dependency in the Makefile.in so that THDF5 will be made before
the thyperslab_wr program.
Platforms tested:
Linux
Purpose:
Fix
Description:
I didn't put the zlib fix into the 1.4 branch.
Solution:
Put the fix into the configure to clear the cache so that configure
always checks for zlib in the fortran/ directory so that it'll be put
in the LFlags macro.
Purpose:
Make T3E happy
Description:
hdf5-1.4.2-pre0 would not build without adding special flag
to disable linker warning #412 for Fortran
Solution:
Disable warning #412
Platforms tested:
T3E
Purpose:
Bug Fix
Description:
During a parallel make session, some modules would get built way
before the modules they depend upon were built.
Solution:
Explicitly put the dependencies in the Makefile.in so that things
will be built in the correct order.
Platforms tested:
modi4 and eirene.
Purpose:
Bug fix for IBM SP F90 || port
Description:
mpxlf90_r compiler does not like "." for current directory
Solution:
Changed "." to "./"
Platforms tested:
NERSC IBM SP (gseaborg)
Purpose:
SP F90 parallel port
Description:
Makefile.in did not have thdf5.lo on the compilation line, that caused linking
problems for the test on SP3 (gseaborg)
Solution:
Added the file name to the compilation line.
Platforms tested:
NERSC IBM SP
Purpose:
Bug Fix
Description:
This puts the changes Elena made into the correct configure file.
(It should go into the acsite.m4 instead of the configure file). This
is only put in the 1.4 branch right now to save messing up the 1.5
branch for now :-).
Purpose:
Bug bypass
Description:
Fortran configure checks flags where to find F90 modules in the
order "M", "I" and "p". On IBM SP "M" is a reserved flag, configure
does not understand compiler's warning and uses it to specify
module directories. Then tests and examples compilation fails since
module directory is not specified correctly on the compilation line.
Solution:
Changed the order of flags to be "I", "M", "p", so configure on IBM SP
finds the correct flag first.
Platforms tested:
IBM SP, Solaris 2.7, Linux, DEC UNIX, HP 11.00, IRIX64 (yes, all of them :-)
Purpose:
Maintenance on IBM SP
Description:
I used unnecessary system specific compiler falgs
Solution:
Removed unnecessary flags
Platforms tested:
NERSC IBM SP (gseaborg)
Purpose:
Windows port
Description:
Names of H5f.c H5ff.f90 files caused linking problems
on Windows platforms.
Solution:
Renamed the files to H5_f.c and H5_ff.f90.
Platforms tested:
Windows 98 and Solaris 2.7.
Purpose:
Windows and DEC OSF port
Description:
Added support for Windows and DEC UNIX (OSF1)
Solution:
Interface blocks for each C function called from corresponding
F90 function were added to port HDF5 F90 Library to Windows platforms.
Special DEC compilers directives were added to avoid name conflicts
for C functions called from F90 functions on Windows and DEC UNIX.
Also changes were done to the h5dwrite/read_f and h5awrite/read_f
interfaces ( extra parameter added to make code portable between
Windows and UNIX platforms)
Platforms tested:
Windows 98 (static library only), DEC UNIX
Purpose:
HPUX 11.00 port
Description:
Redundant "USE" statements triggered F90 compiler bug on HPUX 11.00
systems.
Solution:
Removed redundant "USE" statement as was recommended by HP people.
This fix is different from the fix I applied to 1.5 branch. The
branch does not have Windows port yet (I am waiting for DEC response
on DLL bug). So I decided to make a minimum change to the source code
at this point. Fix applied to 1.5 branch is more consistent but
several other files have to be modified. When I finish Windows port
all F90 files in this branch will be replaced anyway.
Platforms tested:
HPUX 11.00 (kelgia)
Code Update
Description:
Ported change from the 1.5 branch to the 1.4 branch where all HDF5
include files are in quotes instead of angle brackets:
#include "hdf5_file.h"
instead of
#include <hdf5_file.h>
Platforms tested:
Linux
Bug Fix
Description:
If we need to specify a -R flag for dynamic libraries (like, in the
case when we specify --with-hdf4), then this flag needs to be added
to the linking line so that it will show up in the generated library
and other programs linking to that library will be able to find the
relevant libraries.
Solution:
Added the DYNAMIC_DIRS macro to the link line.
Platforms tested:
Arabica
Bug Fix
Description:
testpar/Makefile was being generated even if parallel wasn't
specified.
Solution:
Conditionally create this file only if parallel is specified.
Platforms tested:
Linux
Purpose:
Port to DEC ALPHA running LINUX
Description:
Added necessary definitions to the fortran header file for LINUX port.
Platforms tested:
DEC ALPHA LINUX and DEC OSF
Purpose:
Port to DEC ALPHA running LINUX
Description:
I added alphaev67-linix-gnu configuration files to ./config and ./fortran/config
directories.
Platforms tested:
DEC ALPHA LINUX and DEC OSF
Purpose:
Bug fix
Description:
Function name h5rget_object_type_obj_f was used in test program
instead of the generic name h5rget_object_type_f.
Solution:
Changed the name.
Platforms tested:
Linux (eirene)
Bug fix
Description:
The /bin/csh shell was causing problems if you were using a different
shell than csh (like bash). It couldn't find the compiler.
Solution:
Changed to the more standard /bin/sh
Platforms tested:
Linux
New platform
Description:
Support the Cray SV1 machine. (config file is identical to unicosmk file
right now).
Platforms tested:
Cray SV1 (killeen.nersc.gov)
Purpose:
Bug fix
Description:
Compilation failed for the H5f90global.f90 file on DEC UNIX (hdf5-1.4.0-beta3-pre2)
When new definition H5E_TBBT_F was added, the length of the corresponding
H5E_flags array was not increased.
Solution:
Fixed the length of the array.
Platforms tested:
DEC UNIX (gondolin)
Purpose:
Bug fix.
Description:
While building on T3E, I noticed several compiler warnings about
variable being used before its value was defined.
Solution:
Fixed.
Platforms tested:
T3E (mcurie.nersc.gov)
Bug Fix
Description:
Small bug fix to the acsite.m4 stuff. We should check if the Fortran
9X compiler was found instead of the CC compiler.
Solution:
Changed CC to F9X macro.
Platforms tested:
Linux
Bug Fix
Description:
The test ``test -e "filename"'' doesn't work with some Bourne shells
(for instance, on Arabica).
Solution:
Changed test to ``test -f "filename"''.
Platforms tested:
Arabica
Bug fix
Description:
This should fix the problem with installing the Fortran module
files.
Solution:
This script determines if the HDF5 module is created. If it is,
then we assume that we need to install all of the modules. I
check for both upper and lowercase in the name cause I'm not sure
what weird fortran compilers will do.
Platforms tested:
Linux
Another fix...
Description:
This should work for all platforms now. The other fix didn't work
for the Linux platform
Solution:
Explicitly copy the modules if they exist.
Platforms tested:
Linux
Bug Fix
Description:
When trying to install the Fortran Modules, it would barf if
there weren't any files in the directory with that extension
(i.e., in the test/ directory).
Solution:
Changed the installation to install only those files which
actually have the correct extension we want.
Platforms tested:
This type of fix works on the T3E and Linux
Install Fix
Description:
Fortran modules need to be installed.
Solution:
I check for the extension modules are created with and use that
during the install...
Platforms tested:
Linux
Purpose:
Maintenance
Description:
Not all platforms support F90 MPI. I used USE MPI statement, and
it did not work on T3E (mcurie.nersc.gov)
Solution:
Use INCLUDE 'MPIF.H' statement instead of USE MPI.
Platforms tested:
O2K and T3E
Bug Fix
Description:
Parallel stuff wasn't being compiled on T3E. It was complaining
about not being able to find said files. Also, I was confused
about which Fortran module needed to be compiled when it was
parallel.
Solution:
Did magic so that the correct files are specified when parallel
is enabled.
Platforms tested:
T3E
New Config
Description:
T3E at mcurie.nersc.gov changed it's name yet again.
Solution:
Create new file so that configure will find it correctly.
Platforms tested:
T3E
Bug Fix
Description:
The fix we put in to ignore warning 405 was incorrect. The quotes
were confusing to configure.
Solution:
Turns out that there doesn't need to be a space between the -M
flag and the warning number.
Platforms tested:
T3E
Purpose:
Bug fix on T3E.
Description:
There was a typo in the h5init_types_c name translation line that
caused compilation errors.
Solution:
Fixed the typo. This fix exposes another error and I have no clue what to
do about this one
f90 -p. -p../src -dp -o fortranlib_test fortranlib_test.o hdf5test.o tH5F.o tH5D.o tH5R.o tH5S.o tH5T.o tH5Sselect.o tH5P.o tH5A.o tH5I.o tH5G.o ../src/.libs/libhdf5_fortran.a ../../src/.libs/libhdf5.a -L/u3/epourmal/HDF4/NewHDF/lib -lmfhdf -ldf -ljpeg -lz -lnsl -lm
cld-405 cld: WARNING
The entry point `HDF5' defined in relocatable object `../src/.libs/libhdf5_fortran.a[HDF5.o:HDF5]' is used; the definition in relocatable object `./../src/HDF5.o:HDF5' is ignored.
cld-431 cld: WARNING
The resulting output file `fortranlib_test' is not executable because of previous WARNING messages.
Make: "../../libtool --mode=link f90 -p. -p../src -dp -o fortranlib_test fortranlib_test.lo hdf5test.lo tH5F.lo tH5D.lo tH5R.lo tH5S.lo tH5T.lo tH5Sselect.lo tH5P.lo tH5A.lo tH5I.lo tH5G.lo ../src/libhdf5_fortran.la ../../src/libhdf5.la": Error code 1
cmd-2436 make: Stop.
+ exit 1
Make: "set -x; for d in src test examples; do \
(cd $d && make tests) || exit 1; \
done": Error code 1
Platforms tested:
T3E
Bug Fix
Description:
We were not propagating the FFLAGS macro. I.e., we were
overwriting it after it was set in the commence.in includes.
Solution:
Include it with a ``@FFLAGS@'' where we'd normally overwrite it
so that it isn't.
Platforms tested:
T3E
