Update
Description:
Revamped the configuration system. The configurations for the Fortran
and C++ libraries are no longer separate from the "main"
configuration system. This involved removing the "configure*" and
"aclocal.m4" files from the fortran/ and c++/ subdirectories. Also
merging settings in the config/ subdirectories into the main config/
subdirectory.
Fortran header files had to be modified a little for Linux. It was
checking if it was a Linux machine by some #defines, however with the
-std=c99 switch, these defines weren't there. I added a check for
some other ones which should be there whether the -std=c99 switch is
used or not.
Platforms tested:
Verbena (Fortran & C++)
Sol (Fortran & C++)
Copper (Fortran & C++)
Modi4 (Parallel, Fortran, & C++)
Misc. update:
Code cleanup
Description:
Finish converting the B-tree 'K' values to use unsigned integers, rather
than signed ones, since negative amounts of entries in a B-tree node aren't
meaningful.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Update configuration
Description:
Now that we've split the tree (Yea!), change the main trunk back to debug
on and production off.
Also, change the version # to 1.7.0
update for release
Description:
Set the version information to 1.6.0-pre1 to get ready for
v1.6 release.
Platforms tested:
h5committested.
Misc. update:
Description: When Quincey and I updated Fortran SZIP flags, we accidentally
renamed one of the C flags H5_SZIP_ALLOW_K13_OPTION_MASK used
by Fortran C-stub routine.
Solution: Fix the typo.
Platforms tested: Linux 2.5 and True64
Misc. update:
Purpose:
Bug Fix
Description:
Changes needed to make "pmake" work on Modi4.
Solution:
Needed to add some null macro defines in the commence.in files.
Needed to remove a dependence on LIBH5TEST in the fortran make
since LIBH5TEST isn't used in the fortran stuff.
Platforms tested:
Modi4 (small change)
Misc. update:
Purpose: Bug fix
Description: Makefile.in has hardcoded dependencies. H5Zff.lo was
missing for the sequential version. That caused parallel
make to fail, since module HDF5 was built before H5Z.
Solution: Added H5Zff.lo to dependencies list.
Platforms tested: This is an obvious error and also due to the seminar and picnic
schedule I am checking in without testing. I will test it later today.
Misc. update:
Purpose: Small bug fix
Description: On SP when 64 bit mode is used, RUNPARALLEL environment
variable is not set up correctly for Fortran.
Solution: Copy Albert's fix for C library to Fortran
Platforms tested: copper with 64-bit parallle C and Fortran
Misc. update:
Purpose: Maintenance
Description: Bumped the version number to 1.5.62 after creating
a tar ball for the fourth round of testing.
Solution: run bin/h5vers -s scipt on arabica
Platforms tested: N/A
Misc. update:
Bug Fix
Description:
On Copper, the redefinition of the PACKAGE_* #defined macros
in H5pubconf_fortran.h was causing havoc with the compiler now
that we specify ANSI C with it.
Solution:
Renamed the PACKAGE_* variables to FORTRAN_PACKAGE_* instead.
Platforms tested:
Copper (small fix...needed to determine the sed command worked).
Misc. update:
Purpose: IA64 (titan) cleanup and backing up previous change to the
H5f90global.f90 file
Description: We defined IA64 variable for C-stubs compilation
on IA64 systems. But system defines __ia64 and
it is better to use it as we do on all other systems.
Fortran test failed since global variable became undefined.
Solution: Removed -DIA64 and use __ia64 instead.
Somehow removal of COMMON statements from H5f90global.f90
caused errors on titan. Most of the global fortran variables became
undefined. I am not sure why it is happenning. It may be ecc compiler
or there is an error in the Fortran code. Since it may take some time
to track it, I decided to remove this change.
Platforms tested: titan, arabica
Misc. update:
Purpose: IA64 (titan) cleanup
Description: We defined IA64 variable for C-stubs compilation
on IA64 systems. But system defines __ia64 and
it is better to use it as we do on all other systems.
Solution: Removed -DIA64 from compilation flags since H5f90i.h header
files uses __ia64 variable that is defined on IA64 systems.
Platforms tested: titan
Misc. update:
Purpose: Bug fix
Description: On Cray SV1 multi-driver test failed while closing
access property list.
This test creates a file using multi driver, writes
dataset, closes the file; reopens the file and reads
back data. At some point I commented out call to
h5pget_access_plist_f, but forgot to comment out corresponding
h5pclose_f.
Solution: removed comment on the h5pget_access_plist_f subroutine.
Platforms tested: Cray SV1, copper with parallel, Winodws with VF, arabica.
There is some caveat left. I have a call to h5pget_fapl_multi_f
that follows h5pget_access_plist_f, it was also commented out.
This call works everywhere except Windows. Fortran part looks OK,
since my test program uses h5pget_fapl_multi_f before it closes the
file in the same test, and it works. Probably it is a library
bug that needs confirmation. For now I will leave second
h5pget_fapl_multi_f commented out.
Misc. update:
Purpose: Bug fix
Description: On Windows Fortran szip test failed in debug mode.
It turned out that C-stub for H5Pget_filter_by_id didn't
calculate the correct value of namelen parameter that is
passed to the H5Pget_filter_by_id function. As a result
fortran parameter that hold creation property id was overwritten
and h5fdcreate_f failed.
Solution: Fixed the value of namelen parameter to the H5Pget_filter_by_id
function.
Platforms tested: Windows 2000 with VF both debu and release modes,
sol, verbena.
Misc. update:
Purpose: Code cleanup
Description: For some unknown to myself reason I used COMMON in the
HDF5 module that has to be included in all Fortran
HDF5 application. This is redundant and may cause
problems for optimization. Also COMMON is an "OLD"
feature and shouldn't be used.
Solution: Removed COMMON statements.
Platforms tested: modi4 sequential and parallel, arabica, vebena,
Windows with Visual Fortran.
Misc. update:
Purpose: Small bug fix
Description: Variable flag was declared twice. That caused compilation to fail
on True64 system.
Solution: Deleted one of the declarations.
Platforms tested: True64 at PSC and arabica. Change is trivial, so h5commitest
is not necessary.
Misc. update:
Purpose: Maintenance for the third round of testing
Description: Increased the version number to 1.5.59 after creating
a tar ball for testing.
Solution:
Platforms tested:
Misc. update:
bug fix and cleanup
Description:
Previous change messed things up that fortranlib_test was linked
with multiple MAIN because $(TEST_OBJ) was used as if it was for
fortranlib_test only.
Solution:
Created a separated $(FORTLIBTEST_OBJ) for the fortranlib_test test.
Adjusted other related symbol names.
Also, removed DISTCLEAN=* which held files that should have been
removed in MOSTLYCLEAN.
Platforms tested:
"h5committested" (modi4, sol, verbena).
In the process of running fortran tests in arabica and kelgia.
Misc. update:
cleanup
Description:
Move the removal of libhdf5_fortran.settings from clean to
distclean target.
Platforms tested:
Tested in copper only since the change is trivial.
Misc. update:
Cleanup
Description:
Moved the cleanup of configure generated files to DISTCLEAN as
that should be the place they get removbed.
Platforms tested:
Tested in copper only as change is trivial.
Misc. update:
Improvement
Description:
CHanged test dataset dimension sizes to (120, 240) so that
it can be tested with nprocs equal to 1, 2, 3, 4, 5, 6, 8, ...
Less restrictive than before.
Platforms tested:
only in CU since this is a pretty trivial change.
Misc. update:
Bug Fix
Description:
The Dependencies file wasn't being generated correctly.
Solution:
The depned1.in file had old stuff in it. Replaced it with a copy of
the depend1.in file from the C++ directory.
Platforms tested:
Verbena (Only affects GNU platforms).
Misc. update:
Code cleanup
Description:
h5pset_preserve_f function changed from an INTEGER to a LOGICAL parameter,
change it here too.
Platforms tested:
h5committested
Purpose: Maintenance
Description: Updated test to use new type of the argument for the
h5pset(get)_preserve_f function
Solution:
Platforms tested: arabica nad verbena
Misc. update:
Purpose: Bug fix
Description: One of the arguments to the h5pset(get)_preserve_f and
h5pset(get)_fapl_core_f had fortran INTEGER instead
of LOGICAL type.
Solution: Changed the type
Platforms tested: arabica and verbena
This is a very simple change, and I want to go home :-)
I will be doing more testing anyway on modi4 tomorrow.
Misc. update:
API tweak.
Description:
The H5Sget_select_bounds() API call was using hsize_t arrays for retrieving
the 'start' and 'end' coordinates, which is counter to the rest of the dataspace
API.
Solution:
Change the arrays to be hssize_t instead.
Platforms tested:
FreeBSD 4.8 (sleipnir) w/C++
FreeBSD 4.8 (sleipnir) w/parallel
h5committested
Misc. update:
Updated all docs for this change.
Added 1.4 compatibility #ifdef's
Purpose: Support for Fortran Absoft compiler on Linux
Description: Absoft has its own name translation rules
for the names of C functions called from Fortran
Solution: Added "if defined H5_ABSOFT" statement to the linux portion
of the H5f90i.h file to define correct translations.
For now, Fortran users who use ABSOFT fortran compiler have to specify
-DH5_ABSOFT flag for their C compiler.
Platforms tested: Remote laptop running SuSE8.1 with Absoft compiler,
verbena with icc and ifc just to make sure that
our current linux configuration still works.
Since it is a pure Linux change, I didn't test it on
other systems.
Misc. update:
Purpose: Maintenance for the second round of testing
Description: Used bin/h5vers to change version number to 1.5.55
Solution:
Platforms tested: arabica
Misc. update:
Update
Description:
GPFS should only be checked for if the --enable-gpfs flag is used.
Otherwise, it shouldn't.
Platforms tested:
Linux (Configure only fix so only needed to test it to make sure the
configure does the right thing and that the build won't
break. I need to test it on a machine that has GPFS to make
sure it works there...)
Code Cleanup
Description:
Warning messages were being produced by the "make" program because
the "docdir" was being specified twice as a target in the generated
Makefiles. This is because the "EXAMPLESDIR" was also defined as
"docdir".
Solution:
Made "EXAMPLESDIR" unique for C, Fortran, and C++ in the commence.in
file and removed EXAMPLESDIR from the Makefile.ins
Platforms tested:
Dangermouse (only affects make system, not code).
Misc. update:
Purpose: Maintenance
Description: I changed release version to 1.5.54.
Email about tetsing of 1.5.53 will be send after this checkins.
Solution: used bin/h5vers -s to change the version number
Platforms tested: Done on arabica
Misc. update:
