| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cimmit changes to Makefile.in(s) and H5PL.c that resulted from running
autogen.sh.
Conflicts:
README.txt
c++/src/Makefile.in
fortran/src/Makefile.in
hl/c++/src/Makefile.in
hl/fortran/src/Makefile.in
hl/src/Makefile.in
java/src/jni/Makefile.in
release_docs/RELEASE.txt
src/Makefile.in
|
| |\
| |
| |
| | |
Tested on: h5committest
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since off_t is exposed by the C API, the large file definitions MUST
be exposed so that client code matches the library.
These definitions have been switched back to AM_CPPFLAGS, which is
exported to h5cc, etc. The POSIX and GNU definitions changes from
r26347 have been left as using H5_CPPFLAGS, which is not sent to
h5cc as we don't want to inflict our needs on external users.
Fixes: HDFFV-9152
Tested on: h5committest
|
| |\ \
| |/
| |
| | |
Tested on: h5committest
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
H5_CPPFLAGS,
which is where the rest of the #defines reside.
The key difference is that AM_CPPFLAGS is exported to h5cc. These #defines
are not necessary to consume the HDF5 API and it's bad form to inflict
our build configuration on users. In particular, the GNU/POSIX defines
could easily conflict with a user's.
Fixes: HDFFV-9152
Tested on: h5committest
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Change AC_TRY_RUN TO AC_TRY_COMPILE
Changed all the instances of AC_TRY_RUN for the Fortran and C++ tests to use
AC_COMPILE_IFELSE and moved all the tests to new files in m4 directory:
aclocal_cxx.m4 (for C++ tests)
aclocal_fc.m4 (for Fortran tests)
tested: jam
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Improve configure's large-file support control.
Description:
Modified configure to now attempt to add defines necessary for
supporting largefiles on all systems, instead of solely on linux. This
is in response to user requests to enable largefile support on Solaris
by default, as well as to give extra control on AIX (instead of just
jamming the necessary flag into the config files).
The old --enable-linux-lfs flag has been removed in favor of the
--enable-largefile flag (enabled by default), which can be used on all
platforms.
On systems where large files cannot be supported in this manner,
configure will report as such.
Tested:
h5committest
AIX (NCSA's blue_print machine)
duty, liberty, and linew.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Configure cleanup
Description:
Removed unused macros, migrated to non-depreciated macros.
Solution:
The changes to use standard AC_TRY_LIB macros earlier this week
seem not to have broken anything, so I deleted the local macros in
acsite.m4 (with an eye to eventually deleting the rest of the file and
using only autoconf-supported macros).
Replaced the depreciated AC_TRY_LIB with AC_LIB_IFELSE to shut up
warnings during reconfigure.
Platforms tested:
mir, copper (should be just cleanup)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Automake update cleanup and minor changes
Description:
Removed macros in acsite.m4 that are no longer used.
Switched to using autoconf's AC_LANG_PUSH(Fortran) instead of old
AC_LANG_FORTRAN9X macro.
Switched to using AC_LANG_PUSH() and AC_LANG_POP() (from old AC_LANG_X).
Added ifort to list of Fortran compilers configure will look for.
Added a note about automake change to Release Notes.
Platforms tested:
copper, modi4 (parallel and serial), eirene
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
acsite.m4 contains macros to handle fortran compiler. Some of these macros
are obsolete with automake 1.9.5, but some of them are still used.
These macros need to refer to the fortran compiler as $FC, not $F9X.
Solution:
The version of acsite.m4 with this change didn't get checked in last time.
Oops.
Replaced all occurances of $F9X with $FC and $FFLAGS with $FCFLAGS in
acsite.m4.
Platforms tested:
copper, modi4 (serial and parallel), kelgia, eirene.
Some errors from btree code and ph5diff. No errors in fortran/test.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Fortran module search directories included ../src and
../../fortran/src directories; this was defined in
acsite.m4 file in order for fortran and HL fortran tests
to compile. Those flags were included in h5fc and h5pfc scripts.
Solution: Removed those directories from acsite.m4 file and updated
Makefile.in files.
Platforms tested: sequential on arabica and parallel on copper
including HL Fortran
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
add hl fortran
Description:
Solution:
Platforms tested:
linux (absfot and pgf90)
solaris (32 and 64 bit)
AIX
note : HP gives a compiling error , to be fixed in the future
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
On "user02", the Fortran compiler is "efc". We weren't testing for
this compiler (and I don't know how it was succeeding before...).
Solution:
Added efc to the list of Fortran compilers we check for.
Platforms tested:
Couldn't test as I don't have access to user02. But this doesn't
affect other platforms.
Misc. update:
|
|
|
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:
|
