For make installcheck, compile and run installed examples using the installed scripts. They were being compiled but not run.
Add Fortran2003 examples to the run-ex-fortran script when fortran2003 is enabled.
Set flag to -O3 in production mode for Intel compilers other than those with specified other settings.
Gentoo patches:
Remove unnecessary setting of LD_LIBRARY_PATH from configure.
Prevent potential array subscript out of bounds error in perform/pio_engine.c and sio_engine.c.
Tested with h5committest on jam, koala, ostrich and platypus, on emu and kite, and parallel tests on jam, koala and platypus with mpich built with gnu 4.8.2 and with intel compilers.
Remove all traces of MPI-POSIX VFD and GPFS detection/code.
Remove remaining traces of stream VFD.
Remove testpar/t_posix_compliant test (it's not actually verifying anything).
Clean up H5D__mpio_opt_possible() further.
Moved environment variable that disables MPI collective operations into
MPI-IO VFD (instead of it being in src/H5S.c).
A few other small code cleanups.
Tested on:
Mac OSX/64 10.9.2 (amazon) w/parallel & serial
be found in the standard include and library paths.
Tested on:
32-bit LE linux (jam)
SunOS 5.11 (emu)
64-bit Darwin 12.5 (kite)
64-bit FreeBSD 8.2 (freedom)
Testing focused on making sure that Pthreads could be found on different
platforms and investigating the interaction of Fortran/C++/thread-safe
options.
view objects. The addition of view objects in the fastforward project
is expected to be brough into the trunk sometimes in the future, which
is why we need to make this change.
Tested Manually on Jam and Ostrich.
Tested with h5commitest - Koala with intel compilers failed, but nothing had to do with those changes.
error on Koala: error while loading shared libraries: libirng.so
Threadsafe works in v1.8.10 release. But it fails v1.8.11-pre1 tarball in
configure stage now. There was a typo in the configure around the checking
of pthread library. Fixed it.
Tested: AIX and also h5committested.
This turned out being an issue with configure. The reporter submitted a patch which fixed the fact that we should not be
setting AM_FCFLAGS (an automake variable) with FFLAGS (a user variable).
I removed this, and we now only set FFLAGS if the environment variable is set, otherwise we don't.
Tested: jam (gnu)
