2008-05-15 13:12:00 +08:00
|
|
|
SUMMARY OF THE HDF5 CONFIGURATION
|
|
|
|
|
=================================
|
[svn-r1315] Changes since 19990607
----------------------
./configure.in
./configure [REGENERATED]
./src/libhdf5.settings.in [NEW]
./config/conclude.in
./INSTALL
./MANIFEST
A file called `libhdf5.settings' is installed along with the
libraries and it contains a list of various things that might
be of interest to someone using the library (such as what
compiler/options were used and what other libraries might need
to be linked to satisfy external references). We can add more
things as it becomes necessary. Here's a sample...
SUMMARY OF THE HDF5 CONFIGURATION
=================================
HDF5 Version: hdf5-1.1.106
Configured on: Tue Jun 8 11:38:52 EDT 1999
Configured by: matzke@llnl.gov at Spizella Software
Configure mode: development
Host system: i686-pc-linux-gnulibc1
Byte sex: little-endian
Libraries: static, shared
Parallel support: mpicc
Installation point: /usr/local
Compiler: mpicc (egcs-2.91.66)
Compiler switches: -Wall -g
Extra libraries: -lmfhdf -ldf -lz -ljpeg -lm
Archiver: ar
Ranlib: ranlib
Debugged Packages: d,e,f,g,hg,i,mm,o,p,s,v,z
API Tracing: yes
File addresses: large
1999-06-09 00:14:10 +08:00
|
|
|
|
2008-05-15 13:12:00 +08:00
|
|
|
General Information:
|
|
|
|
|
-------------------
|
2016-01-28 05:45:23 +08:00
|
|
|
HDF5 Version: @H5_VERSION@
|
|
|
|
|
Configured on: @CONFIG_DATE@
|
|
|
|
|
Configured by: @CONFIG_USER@
|
|
|
|
|
Host system: @host_cpu@-@host_vendor@-@host_os@
|
|
|
|
|
Uname information: @UNAME_INFO@
|
|
|
|
|
Byte sex: @BYTESEX@
|
|
|
|
|
Installation point: @prefix@
|
2008-05-15 13:12:00 +08:00
|
|
|
|
|
|
|
|
Compiling Options:
|
|
|
|
|
------------------
|
2016-01-28 05:45:23 +08:00
|
|
|
Build Mode: @BUILD_MODE@
|
|
|
|
|
Debugging Symbols: @SYMBOLS@
|
|
|
|
|
Asserts: @ASSERTS@
|
|
|
|
|
Profiling: @PROFILING@
|
|
|
|
|
Optimization Level: @OPTIMIZATION@
|
|
|
|
|
|
|
|
|
|
Linking Options:
|
|
|
|
|
----------------
|
|
|
|
|
Libraries: @STATIC_SHARED@
|
2013-09-10 22:24:34 +08:00
|
|
|
Statically Linked Executables: @LT_STATIC_EXEC@
|
[svn-r17616] Purpose:
CFLAGS overhaul
Description:
Modified the way configure handles CFLAGS.
(note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS).
1. The configure process will now always preserve a user's CFLAGS
environment variable setup. Any additional flags necessary for compilation
added at configure time will be passed into the Makefiles as AM_CFLAGS,
which is an automake construct to be used in addition to CFLAGS.
This will allow a user to have the final say, as CFLAGS will always appear
later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS
during make will no longer completely erase all flags set by configure,
since they're maintained in AM_CFLAGS.
2. Additionally, where possible, flags previously being assigned directly
into CFLAGS (and thus propagating into h5cc) have now been redirected into
H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into
the h5cc wrapper script as well.
*Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the
Makefiles. Complete description of changes and build process will be
included in a Configure Document that Elena and I are working on.
3. Removed unsupported config files. This includes:
config/dec-osf*
config/hpux11.00
config/irix5.x
config/powerpc-ibm-aix4.x
config/rs6000-ibm-aix5.x
config/unicos*
4. Modified configure summary to display additional values. Specifically,
appropriate AM_* variables are being shown, as well as H5_FCFLAGS and
H5_CXXFLAGS, which were for some reason not already present.
Tested:
- H5committest
- Tested on all THG / NCSA machines, using several combinations of the more
prominent configure options (c++, fortran, szip, threadsafe, parallel,
et cetera). (Thanks to Quincey for rysnc testing setup!)
- With regards to new automated testing, anything *necessary* for
compilation will be caught by the daily tests as it stands now. (i.e.,
if LDFLAGS is not properly set when szip is used, linking will fail).
Additionally, with regards to which flags get into h5cc, if any
*necessary* flags have been improperly removed, then daily tests should
fail during make installcheck. Additional machine-specific desired
behaviors and/or checks may have to be set up separately within the
daily tests, so this is something to work on.
2009-10-08 23:17:30 +08:00
|
|
|
LDFLAGS: @LDFLAGS@
|
2011-04-15 05:21:59 +08:00
|
|
|
H5_LDFLAGS: @H5_LDFLAGS@
|
[svn-r17616] Purpose:
CFLAGS overhaul
Description:
Modified the way configure handles CFLAGS.
(note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS).
1. The configure process will now always preserve a user's CFLAGS
environment variable setup. Any additional flags necessary for compilation
added at configure time will be passed into the Makefiles as AM_CFLAGS,
which is an automake construct to be used in addition to CFLAGS.
This will allow a user to have the final say, as CFLAGS will always appear
later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS
during make will no longer completely erase all flags set by configure,
since they're maintained in AM_CFLAGS.
2. Additionally, where possible, flags previously being assigned directly
into CFLAGS (and thus propagating into h5cc) have now been redirected into
H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into
the h5cc wrapper script as well.
*Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the
Makefiles. Complete description of changes and build process will be
included in a Configure Document that Elena and I are working on.
3. Removed unsupported config files. This includes:
config/dec-osf*
config/hpux11.00
config/irix5.x
config/powerpc-ibm-aix4.x
config/rs6000-ibm-aix5.x
config/unicos*
4. Modified configure summary to display additional values. Specifically,
appropriate AM_* variables are being shown, as well as H5_FCFLAGS and
H5_CXXFLAGS, which were for some reason not already present.
Tested:
- H5committest
- Tested on all THG / NCSA machines, using several combinations of the more
prominent configure options (c++, fortran, szip, threadsafe, parallel,
et cetera). (Thanks to Quincey for rysnc testing setup!)
- With regards to new automated testing, anything *necessary* for
compilation will be caught by the daily tests as it stands now. (i.e.,
if LDFLAGS is not properly set when szip is used, linking will fail).
Additionally, with regards to which flags get into h5cc, if any
*necessary* flags have been improperly removed, then daily tests should
fail during make installcheck. Additional machine-specific desired
behaviors and/or checks may have to be set up separately within the
daily tests, so this is something to work on.
2009-10-08 23:17:30 +08:00
|
|
|
AM_LDFLAGS: @AM_LDFLAGS@
|
2016-01-28 05:45:23 +08:00
|
|
|
Extra libraries: @LIBS@
|
|
|
|
|
Archiver: @AR@
|
2017-11-13 15:22:39 +08:00
|
|
|
AR_FLAGS: @AR_FLAGS@
|
2016-01-28 05:45:23 +08:00
|
|
|
Ranlib: @RANLIB@
|
2008-05-15 13:12:00 +08:00
|
|
|
|
|
|
|
|
Languages:
|
|
|
|
|
----------
|
2016-01-28 05:45:23 +08:00
|
|
|
C: yes
|
|
|
|
|
C Compiler: @CC_VERSION@
|
|
|
|
|
CPPFLAGS: @CPPFLAGS@
|
|
|
|
|
H5_CPPFLAGS: @H5_CPPFLAGS@
|
|
|
|
|
AM_CPPFLAGS: @AM_CPPFLAGS@
|
|
|
|
|
C Flags: @CFLAGS@
|
|
|
|
|
H5 C Flags: @H5_CFLAGS@
|
|
|
|
|
AM C Flags: @AM_CFLAGS@
|
|
|
|
|
Shared C Library: @enable_shared@
|
|
|
|
|
Static C Library: @enable_static@
|
|
|
|
|
|
|
|
|
|
|
2008-05-15 13:12:00 +08:00
|
|
|
Fortran: @HDF_FORTRAN@
|
2010-07-09 10:52:14 +08:00
|
|
|
@BUILD_FORTRAN_CONDITIONAL_TRUE@ Fortran Compiler: @FC_VERSION@
|
2008-10-26 09:47:53 +08:00
|
|
|
@BUILD_FORTRAN_CONDITIONAL_TRUE@ Fortran Flags: @FCFLAGS@
|
[svn-r17616] Purpose:
CFLAGS overhaul
Description:
Modified the way configure handles CFLAGS.
(note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS).
1. The configure process will now always preserve a user's CFLAGS
environment variable setup. Any additional flags necessary for compilation
added at configure time will be passed into the Makefiles as AM_CFLAGS,
which is an automake construct to be used in addition to CFLAGS.
This will allow a user to have the final say, as CFLAGS will always appear
later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS
during make will no longer completely erase all flags set by configure,
since they're maintained in AM_CFLAGS.
2. Additionally, where possible, flags previously being assigned directly
into CFLAGS (and thus propagating into h5cc) have now been redirected into
H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into
the h5cc wrapper script as well.
*Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the
Makefiles. Complete description of changes and build process will be
included in a Configure Document that Elena and I are working on.
3. Removed unsupported config files. This includes:
config/dec-osf*
config/hpux11.00
config/irix5.x
config/powerpc-ibm-aix4.x
config/rs6000-ibm-aix5.x
config/unicos*
4. Modified configure summary to display additional values. Specifically,
appropriate AM_* variables are being shown, as well as H5_FCFLAGS and
H5_CXXFLAGS, which were for some reason not already present.
Tested:
- H5committest
- Tested on all THG / NCSA machines, using several combinations of the more
prominent configure options (c++, fortran, szip, threadsafe, parallel,
et cetera). (Thanks to Quincey for rysnc testing setup!)
- With regards to new automated testing, anything *necessary* for
compilation will be caught by the daily tests as it stands now. (i.e.,
if LDFLAGS is not properly set when szip is used, linking will fail).
Additionally, with regards to which flags get into h5cc, if any
*necessary* flags have been improperly removed, then daily tests should
fail during make installcheck. Additional machine-specific desired
behaviors and/or checks may have to be set up separately within the
daily tests, so this is something to work on.
2009-10-08 23:17:30 +08:00
|
|
|
@BUILD_FORTRAN_CONDITIONAL_TRUE@ H5 Fortran Flags: @H5_FCFLAGS@
|
|
|
|
|
@BUILD_FORTRAN_CONDITIONAL_TRUE@ AM Fortran Flags: @AM_FCFLAGS@
|
[svn-r20475] Purpose:
- Revise shared Fortran library disabling scenarios in configure
- Improve configure output summary
Description:
Shared Fortran libraries are not supported on Mac, but were being
disabled by configure in a way that also forced the C libraries
to be static-only. This has been fixed, so now only shared Fortran
is disabled while shared C can remain.
This prompted two additional changes:
1. While working on the check that addresses whether or not
shared Fortran libraries are allowed, removed old and no
longer needed check(s) that disable shared Fortran
libraries with HP, Intel 8, PGI, and Absoft compilers.
(Essentially, Mac is the only situation in which Fortran
shared are disabled by configure.)
2. Having two different states of libraries (i.e. shared C
library with static-only Fortran library) was not apparent
in the configure summary, which labeled all libraries as
either shared and/or static. I've added lines to both the
C++ and Fortran output sections to list shared/static-ness
of these libraries specifically.
Additionally, I've made sure that the new --enable-unsupported
configure option correctly overrides configure if it tries to
disable a shared library.
Tested:
jam, fred, & h5committest
2011-04-12 05:00:38 +08:00
|
|
|
@BUILD_FORTRAN_CONDITIONAL_TRUE@ Shared Fortran Library: @H5_FORTRAN_SHARED@
|
|
|
|
|
@BUILD_FORTRAN_CONDITIONAL_TRUE@ Static Fortran Library: @enable_static@
|
|
|
|
|
|
2008-05-15 13:12:00 +08:00
|
|
|
C++: @HDF_CXX@
|
2010-07-09 10:52:14 +08:00
|
|
|
@BUILD_CXX_CONDITIONAL_TRUE@ C++ Compiler: @CXX_VERSION@
|
2008-10-26 09:47:53 +08:00
|
|
|
@BUILD_CXX_CONDITIONAL_TRUE@ C++ Flags: @CXXFLAGS@
|
[svn-r17616] Purpose:
CFLAGS overhaul
Description:
Modified the way configure handles CFLAGS.
(note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS).
1. The configure process will now always preserve a user's CFLAGS
environment variable setup. Any additional flags necessary for compilation
added at configure time will be passed into the Makefiles as AM_CFLAGS,
which is an automake construct to be used in addition to CFLAGS.
This will allow a user to have the final say, as CFLAGS will always appear
later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS
during make will no longer completely erase all flags set by configure,
since they're maintained in AM_CFLAGS.
2. Additionally, where possible, flags previously being assigned directly
into CFLAGS (and thus propagating into h5cc) have now been redirected into
H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into
the h5cc wrapper script as well.
*Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the
Makefiles. Complete description of changes and build process will be
included in a Configure Document that Elena and I are working on.
3. Removed unsupported config files. This includes:
config/dec-osf*
config/hpux11.00
config/irix5.x
config/powerpc-ibm-aix4.x
config/rs6000-ibm-aix5.x
config/unicos*
4. Modified configure summary to display additional values. Specifically,
appropriate AM_* variables are being shown, as well as H5_FCFLAGS and
H5_CXXFLAGS, which were for some reason not already present.
Tested:
- H5committest
- Tested on all THG / NCSA machines, using several combinations of the more
prominent configure options (c++, fortran, szip, threadsafe, parallel,
et cetera). (Thanks to Quincey for rysnc testing setup!)
- With regards to new automated testing, anything *necessary* for
compilation will be caught by the daily tests as it stands now. (i.e.,
if LDFLAGS is not properly set when szip is used, linking will fail).
Additionally, with regards to which flags get into h5cc, if any
*necessary* flags have been improperly removed, then daily tests should
fail during make installcheck. Additional machine-specific desired
behaviors and/or checks may have to be set up separately within the
daily tests, so this is something to work on.
2009-10-08 23:17:30 +08:00
|
|
|
@BUILD_CXX_CONDITIONAL_TRUE@ H5 C++ Flags: @H5_CXXFLAGS@
|
|
|
|
|
@BUILD_CXX_CONDITIONAL_TRUE@ AM C++ Flags: @AM_CXXFLAGS@
|
2015-04-13 16:25:56 +08:00
|
|
|
@BUILD_CXX_CONDITIONAL_TRUE@ Shared C++ Library: @enable_shared@
|
[svn-r20475] Purpose:
- Revise shared Fortran library disabling scenarios in configure
- Improve configure output summary
Description:
Shared Fortran libraries are not supported on Mac, but were being
disabled by configure in a way that also forced the C libraries
to be static-only. This has been fixed, so now only shared Fortran
is disabled while shared C can remain.
This prompted two additional changes:
1. While working on the check that addresses whether or not
shared Fortran libraries are allowed, removed old and no
longer needed check(s) that disable shared Fortran
libraries with HP, Intel 8, PGI, and Absoft compilers.
(Essentially, Mac is the only situation in which Fortran
shared are disabled by configure.)
2. Having two different states of libraries (i.e. shared C
library with static-only Fortran library) was not apparent
in the configure summary, which labeled all libraries as
either shared and/or static. I've added lines to both the
C++ and Fortran output sections to list shared/static-ness
of these libraries specifically.
Additionally, I've made sure that the new --enable-unsupported
configure option correctly overrides configure if it tries to
disable a shared library.
Tested:
jam, fred, & h5committest
2011-04-12 05:00:38 +08:00
|
|
|
@BUILD_CXX_CONDITIONAL_TRUE@ Static C++ Library: @enable_static@
|
2008-05-15 13:12:00 +08:00
|
|
|
|
2016-03-22 15:22:52 +08:00
|
|
|
Java: @HDF_JAVA@
|
|
|
|
|
@BUILD_JAVA_CONDITIONAL_TRUE@ Java Compiler: @JAVA_VERSION@
|
|
|
|
|
|
2016-02-29 10:43:00 +08:00
|
|
|
|
2008-05-15 13:12:00 +08:00
|
|
|
Features:
|
|
|
|
|
---------
|
2018-07-27 01:50:26 +08:00
|
|
|
Parallel HDF5: @PARALLEL@
|
|
|
|
|
Parallel Filtered Dataset Writes: @PARALLEL_FILTERED_WRITES@
|
2018-08-01 02:42:19 +08:00
|
|
|
Large Parallel I/O: @LARGE_PARALLEL_IO@
|
2018-07-27 01:50:26 +08:00
|
|
|
High-level library: @HDF5_HL@
|
2019-06-12 23:21:41 +08:00
|
|
|
Build HDF5 Tests: @HDF5_TESTS@
|
2019-06-25 15:32:32 +08:00
|
|
|
Build HDF5 Tools: @HDF5_TOOLS@
|
2018-07-27 01:50:26 +08:00
|
|
|
Threadsafety: @THREADSAFE@
|
|
|
|
|
Default API mapping: @DEFAULT_API_VERSION@
|
|
|
|
|
With deprecated public symbols: @DEPRECATED_SYMBOLS@
|
|
|
|
|
I/O filters (external): @EXTERNAL_FILTERS@
|
|
|
|
|
MPE: @MPE@
|
2019-08-14 14:07:48 +08:00
|
|
|
Map (H5M) API: @MAP_API@
|
2018-07-27 01:50:26 +08:00
|
|
|
Direct VFD: @DIRECT_VFD@
|
2019-07-26 00:36:37 +08:00
|
|
|
(Read-Only) S3 VFD: @ROS3_VFD@
|
|
|
|
|
(Read-Only) HDFS VFD: @HAVE_LIBHDFS@
|
2018-07-27 01:50:26 +08:00
|
|
|
dmalloc: @HAVE_DMALLOC@
|
|
|
|
|
Packages w/ extra debug output: @INTERNAL_DEBUG_OUTPUT@
|
|
|
|
|
API tracing: @TRACE_API@
|
|
|
|
|
Using memory checker: @USINGMEMCHECKER@
|
|
|
|
|
Memory allocation sanity checks: @MEMORYALLOCSANITYCHECK@
|
|
|
|
|
Function stack tracing: @CODESTACK@
|
|
|
|
|
Strict file format checks: @STRICT_FORMAT_CHECKS@
|
|
|
|
|
Optimization instrumentation: @INSTRUMENT_LIBRARY@
|
