2012-09-12 04:11:44 +08:00
## Process this file with autoconf to produce configure.
##
## Copyright by The HDF Group.
## Copyright by the Board of Trustees of the University of Illinois.
## All rights reserved.
##
## This file is part of HDF5. The full HDF5 copyright notice, including
## terms governing use, modification, and redistribution, is contained in
2017-04-18 03:32:16 +08:00
## the COPYING file, which can be found at the root of the source code
## distribution tree, or in https://support.hdfgroup.org/ftp/HDF5/releases.
## If you do not have access to either file, you may request a copy from
## help@hdfgroup.org.
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Initialize configure.
##
2013-01-12 03:00:50 +08:00
AC_REVISION($Id: configure.ac 22697 2012-08-19 14:35:47Z hdftest $)
2012-09-12 04:11:44 +08:00
AC_PREREQ([2.69])
## AC_INIT takes the name of the package, the version number, and an
## email address to report bugs. AC_CONFIG_SRCDIR takes a unique file
## as its argument.
##
## NOTE: Do not forget to change the version number here when we do a
## release!!!
##
2017-03-21 06:14:16 +08:00
AC_INIT([HDF5], [1.11.0], [help@hdfgroup.org])
2015-08-11 22:35:30 +08:00
2002-04-24 04:02:26 +08:00
AC_CONFIG_SRCDIR([src/H5.c])
2015-09-01 14:30:21 +08:00
AC_CONFIG_HEADERS([src/H5config.h])
2002-04-24 04:02:26 +08:00
AC_CONFIG_AUX_DIR([bin])
2010-09-10 23:45:07 +08:00
AC_CONFIG_MACRO_DIR([m4])
2005-05-26 06:32:22 +08:00
2012-09-12 04:11:44 +08:00
## AM_INIT_AUTOMAKE takes a list of options that should be applied to
## every Makefile.am when automake is run.
2016-11-10 15:00:58 +08:00
AM_INIT_AUTOMAKE([foreign subdir-objects])
2017-03-09 23:54:19 +08:00
m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) # use silent rules where available - automake 1.11
2002-04-24 04:02:26 +08:00
2012-09-12 04:11:44 +08:00
## AM_MAINTAINER_MODE turns off "rebuild rules" that contain dependencies
2015-02-21 17:41:03 +08:00
## for Makefiles, configure, src/H5config.h, etc. If AM_MAINTAINER_MODE
## is enabled, these files will be rebuilt if out of date. This is a
## problem because if users try to build on a machine with
2012-09-12 04:11:44 +08:00
## the wrong versions of autoconf and automake, these files will be
## rebuilt with the wrong versions and bad things can happen.
## Also, CVS doesn't preserve dependencies between timestamps, so
## Makefiles will often think rebuilding needs to occur when it doesn't.
2015-02-21 17:41:03 +08:00
##
## By default, it is enabled. Users can configure with
## --disable-maintainer-mode to prevent running the autotools.
AM_MAINTAINER_MODE([enable])
2005-02-03 04:59:46 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Set prefix default (install directory) to a directory in the build area.
## This allows multiple src-dir builds within one host.
AC_PREFIX_DEFAULT([`pwd`/hdf5])
## Run post processing on files created by configure.
## src/H5pubconf.h:
## Generate src/H5pubconf.h from src/H5config.h by prepending H5_ to all
## macro names. This avoid name conflict between HDF5 macro names and those
## generated by another software package that uses the HDF5 library.
## src/libhdf5.settings:
## Remove all lines begun with "#" which are generated by CONDITIONAL's of
## configure.
AC_CONFIG_COMMANDS([pubconf], [
2001-09-28 07:05:16 +08:00
echo "creating src/H5pubconf.h"
sed 's/#define /#define H5_/' <src/H5config.h |\
sed 's/#undef /#undef H5_/' >pubconf
if test ! -f src/H5pubconf.h; then
/bin/mv -f pubconf src/H5pubconf.h
elif (diff pubconf src/H5pubconf.h >/dev/null); then
2007-02-07 02:50:04 +08:00
rm -f pubconf
2001-09-28 07:05:16 +08:00
echo "src/H5pubconf.h is unchanged"
else
/bin/mv -f pubconf src/H5pubconf.h
fi
2008-05-15 13:12:00 +08:00
echo "Post process src/libhdf5.settings"
sed '/^#/d' < src/libhdf5.settings > libhdf5.settings.TMP
cp libhdf5.settings.TMP src/libhdf5.settings
rm -f libhdf5.settings.TMP
1999-11-17 03:08:14 +08:00
])
2002-04-24 04:02:26 +08:00
2012-09-12 04:11:44 +08:00
## It's possible to configure for a host other than the one on which
## configure is currently running by using the --host=foo flag.
## For machines on which HDF5 is often configured, it can be convenient
## to specify the name of the machine rather than its canonical type.
2015-09-09 04:03:41 +08:00
##
## There are currently no hosts, but if there were they would be
## listed by hostname and the alias would point to a file in
## the config directory:
##
##case $host_alias in
## <some host>)
## host_alias=<config file in config directory>
## ;;
##esac
2005-06-21 01:33:22 +08:00
1997-08-16 00:35:53 +08:00
AC_CANONICAL_HOST
2002-07-18 00:10:46 +08:00
AC_SUBST([CPPFLAGS])
2016-02-29 10:43:00 +08:00
AC_SUBST([JNIFLAGS])
1997-08-16 00:35:53 +08:00
2012-09-12 04:11:44 +08:00
## H5_CFLAGS (and company) are for CFLAGS that should be used on HDF5, but
## not exported to h5cc (or h5fc, etc.)
2005-09-17 05:26:17 +08:00
AC_SUBST([H5_CFLAGS])
AC_SUBST([H5_CPPFLAGS])
2006-04-22 03:21:24 +08:00
AC_SUBST([H5_FCFLAGS])
2005-09-17 05:26:17 +08:00
AC_SUBST([H5_CXXFLAGS])
2016-02-29 10:43:00 +08:00
AC_SUBST([H5_JNIFLAGS])
AC_SUBST([H5_JAVACFLAGS])
AC_SUBST([H5_JAVAFLAGS])
2011-04-15 05:21:59 +08:00
AC_SUBST([H5_LDFLAGS])
2005-09-17 05:26:17 +08:00
2012-09-12 04:11:44 +08:00
## AM_CFLAGS (and company) are for CFLAGS that should be used on HDF5,
## and WILL be exported to h5cc (or h5fc, etc) if set by configure.
[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
AC_SUBST([AM_CFLAGS])
AC_SUBST([AM_FCFLAGS])
AC_SUBST([AM_CXXFLAGS])
AC_SUBST([AM_CPPFLAGS])
2016-02-29 10:43:00 +08:00
AC_SUBST([AM_JNIFLAGS])
AC_SUBST([AM_JAVACFLAGS])
AC_SUBST([AM_JAVAFLAGS])
[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
AC_SUBST([AM_LDFLAGS])
2015-03-31 02:55:21 +08:00
## Make sure flags are initialized.
[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_CFLAGS="${AM_CFLAGS}"
AM_CXXFLAGS="${AM_CXXFLAGS}"
AM_FCFLAGS="${AM_FCFLAGS}"
AM_CPPFLAGS="${AM_CPPFLAGS}"
2016-02-29 10:43:00 +08:00
AM_JNIFLAGS="${AM_JNIFLAGS}"
AM_JAVACFLAGS="${AM_JAVACFLAGS}"
AM_JAVAFLAGS="${AM_JAVAFLAGS}"
2014-12-20 03:50:58 +08:00
AM_LDFLAGS="${AM_LDFLAGS}"
2006-04-27 05:19:21 +08:00
CFLAGS="${CFLAGS}"
CXXFLAGS="${CXXFLAGS}"
FCFLAGS="${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
CPPFLAGS="${CPPFLAGS}"
2016-02-29 10:43:00 +08:00
JNIFLAGS="${JNIFLAGS}"
JAVACFLAGS="${JAVACFLAGS}"
JAVAFLAGS="${JAVAFLAGS}"
[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}"
2012-09-12 04:11:44 +08:00
## Configure may need to alter any of the *FLAGS variables in order for
## various checks to work correctly. Save the user's value here so it
## can be restored once all configure checks are complete.
2009-10-14 05:55:21 +08:00
saved_user_CFLAGS="$CFLAGS"
saved_user_CXXFLAGS="$CXXFLAGS"
saved_user_FCFLAGS="$FCFLAGS"
2016-02-29 10:43:00 +08:00
saved_user_JAVACFLAGS="$JAVACFLAGS"
saved_user_JAVAFLAGS="$JAVAFLAGS"
[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
saved_user_LDFLAGS="$LDFLAGS"
saved_user_CPPFLAGS="$CPPFLAGS"
2006-04-27 05:19:21 +08:00
2012-09-12 04:11:44 +08:00
## Support F9X variable to define Fortran compiler if FC variable is
## not used. This should be deprecated in the future.
2005-03-10 02:48:23 +08:00
if test "x" = "x$FC"; then
FC=${F9X}
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Dump all shell variables values.
##
2002-07-18 00:10:46 +08:00
AC_MSG_CHECKING([shell variables initial values])
set >&AS_MESSAGE_LOG_FD
AC_MSG_RESULT([done])
1999-02-11 23:56:15 +08:00
2016-01-28 05:45:23 +08:00
## ----------------------------------------------------------------------
## Save system information for the library settings file.
##
AC_SUBST([UNAME_INFO])
UNAME_INFO=`uname -a`
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Some platforms have broken basename, and/or xargs programs. Check
## that it actually does what it's supposed to do. Catch this early
2015-06-17 05:25:03 +08:00
## since configure and scripts relies upon them heavily and there's
2015-03-31 02:55:21 +08:00
## no use continuing if it's broken.
2012-09-12 04:11:44 +08:00
##
2003-10-29 01:57:10 +08:00
AC_MSG_CHECKING([if basename works])
BASENAME_TEST="`basename /foo/bar/baz/qux/basename_works`"
if test $BASENAME_TEST != "basename_works"; then
AC_MSG_ERROR([basename program doesn't work])
else
AC_MSG_RESULT([yes])
fi
2015-03-31 02:55:21 +08:00
## xargs basename used in configure to get the CC_BASENAME value
2003-10-29 01:57:10 +08:00
AC_MSG_CHECKING([if xargs works])
XARGS_TEST="`echo /foo/bar/baz/qux/xargs_works | xargs basename`"
if test $XARGS_TEST != "xargs_works"; then
AC_MSG_ERROR([xargs program doesn't work])
else
AC_MSG_RESULT([yes])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check that the cache file was build on the same host as what we're
## running on now.
##
2002-07-18 00:10:46 +08:00
AC_CACHE_CHECK([for cached host], [hdf5_cv_host], [hdf5_cv_host="none"]);
1997-08-16 00:35:53 +08:00
if test $hdf5_cv_host = "none"; then
2001-09-28 07:05:16 +08:00
hdf5_cv_host=$host
1997-08-16 00:35:53 +08:00
elif test $hdf5_cv_host != $host; then
2001-09-28 07:05:16 +08:00
echo "The config.cache file was generated on $hdf5_cv_host but"
echo "this is $host. Please remove that file and try again."
2012-09-12 04:11:44 +08:00
AC_MSG_ERROR([config.cache file is invalid])
1997-08-16 00:35:53 +08:00
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Source any special files that we need. These files normally aren't
## present but can be used by the maintainers to fine tune things like
## turning on debug or profiling flags for the compiler. The search order
## is:
##
2016-03-01 22:50:49 +08:00
## CPU-VENDOR-OS
## VENDOR-OS
## CPU-OS
## CPU-VENDOR
## OS
## VENDOR
## CPU
2012-09-12 04:11:44 +08:00
##
## If the `OS' ends with a version number then remove it. For instance,
## `freebsd3.1' would become `freebsd'
2012-06-05 01:05:02 +08:00
1999-03-03 01:15:35 +08:00
case $host_os in
2011-04-16 04:10:47 +08:00
aix*)
host_os_novers=aix
2010-09-23 06:52:55 +08:00
;;
2001-09-28 07:05:16 +08:00
freebsd*)
host_os_novers=freebsd
;;
2015-09-02 00:12:53 +08:00
solaris*)
host_os_novers=solaris
2001-09-28 07:05:16 +08:00
;;
*)
host_os_novers=$host_os
;;
1999-03-03 01:15:35 +08:00
esac
1998-11-13 23:06:06 +08:00
1998-07-09 02:41:04 +08:00
host_config="none"
1999-03-13 02:35:04 +08:00
for f in $host_cpu-$host_vendor-$host_os \
2002-04-23 07:44:41 +08:00
$host_cpu-$host_vendor-$host_os_novers \
$host_vendor-$host_os \
1999-03-03 01:15:35 +08:00
$host_vendor-$host_os_novers \
2002-04-23 07:44:41 +08:00
$host_cpu-$host_os \
1999-03-03 01:15:35 +08:00
$host_cpu-$host_os_novers \
1998-02-14 02:11:35 +08:00
$host_cpu-$host_vendor \
2002-04-23 07:44:41 +08:00
$host_os \
$host_os_novers \
$host_vendor \
$host_cpu ; do
2002-07-18 00:10:46 +08:00
AC_MSG_CHECKING([for config $f])
2001-08-02 05:00:25 +08:00
if test -f "$srcdir/config/$f"; then
host_config=$srcdir/config/$f
2002-07-18 00:10:46 +08:00
AC_MSG_RESULT([found])
2001-08-02 05:00:25 +08:00
break
fi
2002-07-18 00:10:46 +08:00
AC_MSG_RESULT([no])
1997-08-16 00:35:53 +08:00
done
2003-01-24 03:19:02 +08:00
if test "X$host_config" != "Xnone"; then
2001-09-28 07:05:16 +08:00
CC_BASENAME="`echo $CC | cut -f1 -d' ' | xargs basename 2>/dev/null`"
2001-08-02 05:00:25 +08:00
. $host_config
1997-08-16 00:35:53 +08:00
fi
2012-09-12 04:11:44 +08:00
## Source any special site-specific file
2000-10-04 06:28:31 +08:00
hname="`hostname`"
while test -n "$hname"; do
2001-08-02 05:00:25 +08:00
file=$srcdir/config/site-specific/host-$hname
2002-07-18 00:10:46 +08:00
AC_MSG_CHECKING([for config $file])
2001-08-02 05:00:25 +08:00
if test -f "$file"; then
. $file
2002-07-18 00:10:46 +08:00
AC_MSG_RESULT([found])
2001-08-02 05:00:25 +08:00
break
fi
2002-07-18 00:10:46 +08:00
AC_MSG_RESULT([no])
2001-08-02 05:00:25 +08:00
hname_tmp=$hname
hname="`echo $hname | cut -d. -f2-99`"
test "$hname_tmp" = "$hname" && break
2000-10-04 06:28:31 +08:00
done
2016-07-19 02:37:17 +08:00
2016-02-17 06:42:40 +08:00
## ----------------------------------------------------------------------
## Determine build mode (debug, production, clean).
## This has to be done early since the build mode is referred to
## frequently.
##
AC_MSG_CHECKING([build mode])
AC_ARG_ENABLE([build-mode],
[AS_HELP_STRING([--enable-build-mode=(debug|production|clean)],
[Sets the build mode. Debug turns on symbols, API
tracing, asserts, and debug optimization,
as well as several other minor configure options
that aid in debugging.
Production turns high optimizations on.
Clean turns nothing on and disables optimization
(i.e.: a 'clean slate' configuration).
All these settings can be overridden by using
specific configure flags.
[default=debug]
])],
[BUILD_MODE=$enableval])
## Set the default
## Depends on branch, set via script at branch creation time
if test "X-$BUILD_MODE" = X- ; then
BUILD_MODE=debug
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([BUILD_MODE])
case "X-$BUILD_MODE" in
X-clean)
AC_MSG_RESULT([clean])
;;
X-debug)
AC_DEFINE([DEBUG_BUILD], [1], [Define if this is a debug build.])
H5_CFLAGS="$H5_CFLAGS $DEBUG_CFLAGS"
H5_CPPFLAGS="$H5_CPPFLAGS $DEBUG_CPPFLAGS"
H5_CXXFLAGS="$H5_CXXFLAGS $DEBUG_CXXFLAGS"
H5_FCFLAGS="$H5_FCFLAGS $DEBUG_FCFLAGS"
AC_MSG_RESULT([debug])
;;
X-production)
H5_CFLAGS="$H5_CFLAGS $PROD_CFLAGS"
H5_CPPFLAGS="$H5_CPPFLAGS $PROD_CPPFLAGS"
H5_CXXFLAGS="$H5_CXXFLAGS $PROD_CXXFLAGS"
H5_FCFLAGS="$H5_FCFLAGS $PROD_FCFLAGS"
AC_MSG_RESULT([production])
;;
*)
AC_MSG_ERROR([Unrecognized build mode: $BUILD_MODE. Use debug, production, or clean.])
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Some built-in configure checks can only see CFLAGS (not AM_CFLAGS), so
## we need to add this in so configure works as intended. We will need to
## reset this value at the end of configure, to preserve the user's settings.
2009-10-19 11:05:25 +08:00
CFLAGS="${AM_CFLAGS} ${CFLAGS}"
FCFLAGS="${AM_FCFLAGS} ${FCFLAGS}"
2016-02-29 10:43:00 +08:00
JAVACFLAGS="${AM_JAVACFLAGS} ${JAVACFLAGS}"
JAVAFLAGS="${AM_JAVAFLAGS} ${JAVAFLAGS}"
2009-10-19 11:05:25 +08:00
CXXFLAGS="${AM_CXXFLAGS} ${CXXFLAGS}"
CPPFLAGS="${AM_CPPFLAGS} ${CPPFLAGS}"
LDFLAGS="${AM_LDFLAGS} ${LDFLAGS}"
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Enable dependency tracking unless the configure options or a
## site-specific file told us not to. This prevents configure from
## silently disabling dependencies for some compilers.
##
2005-03-15 04:35:55 +08:00
if test -z "${enable_dependency_tracking}"; then
enable_dependency_tracking="yes"
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check for programs.
##
1997-08-16 00:35:53 +08:00
AC_PROG_CC
2001-09-28 07:05:16 +08:00
CC_BASENAME="`echo $CC | cut -f1 -d' ' | xargs basename 2>/dev/null`"
2000-09-08 04:57:34 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------------
## Configure disallows unsupported combinations of options. However, users
## may want to override and build with unsupported combinations for their
## own use. They can use the --enable-unsupported configure flag, which
## ignores any errors from configure due to incompatible flags.
2010-11-18 02:07:51 +08:00
AC_MSG_CHECKING([if unsupported combinations of configure options are allowed])
AC_ARG_ENABLE([unsupported],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-unsupported],
2010-11-18 02:07:51 +08:00
[Allow unsupported combinations of configure options])],
[ALLOW_UNSUPPORTED=$enableval])
2015-06-17 05:25:03 +08:00
case "X-$ALLOW_UNSUPPORTED" in
2010-11-18 02:07:51 +08:00
X-|X-no)
AC_MSG_RESULT([no])
;;
X-yes)
AC_MSG_RESULT([yes])
;;
*)
;;
esac
2015-08-11 22:35:30 +08:00
## ----------------------------------------------------------------------
## Data types and their sizes.
##
AC_TYPE_OFF_T
AC_CHECK_TYPE([size_t], [],
[AC_DEFINE_UNQUOTED([size_t], [unsigned long],
[Define to `unsigned long' if <sys/types.h> does not define.])])
AC_CHECK_TYPE([ssize_t], [],
[AC_DEFINE_UNQUOTED([ssize_t], [long],
[Define to `long' if <sys/types.h> does not define.])])
AC_CHECK_TYPE([ptrdiff_t], [],
[AC_DEFINE_UNQUOTED([ptrdiff_t], [long],
[Define to `long' if <sys/types.h> does not define.])])
AC_C_BIGENDIAN
2015-12-03 10:45:08 +08:00
AC_CHECK_SIZEOF([char])
AC_CHECK_SIZEOF([short])
AC_CHECK_SIZEOF([int])
AC_CHECK_SIZEOF([unsigned])
AC_CHECK_SIZEOF([long])
AC_CHECK_SIZEOF([long long])
AC_CHECK_SIZEOF([__int64])
AC_CHECK_SIZEOF([float])
AC_CHECK_SIZEOF([double])
AC_CHECK_SIZEOF([long double])
2015-08-11 22:35:30 +08:00
2016-01-28 05:45:23 +08:00
## ----------------------------------------------------------------------
2015-08-11 22:35:30 +08:00
## Check for non-standard extenstion __FLOAT128
2016-01-28 05:45:23 +08:00
##
2015-08-11 22:35:30 +08:00
HAVE_FLOAT128=0
HAVE_QUADMATH=0
FLT128_DIG=0
LDBL_DIG=0
AC_CHECK_SIZEOF([__float128])
AC_CHECK_SIZEOF([_Quad])
AC_CHECK_HEADERS([quadmath.h], [HAVE_QUADMATH=1], [])
PAC_FC_LDBL_DIG
2016-01-28 05:45:23 +08:00
AC_SUBST([PAC_C_MAX_REAL_PRECISION])
2015-08-11 22:35:30 +08:00
if test "$ac_cv_sizeof___float128" != 0 && test "$FLT128_DIG" != 0 ; then
AC_DEFINE([HAVE_FLOAT128], [1], [Determine if __float128 is available])
PAC_C_MAX_REAL_PRECISION=$FLT128_DIG
else
PAC_C_MAX_REAL_PRECISION=$LDBL_DIG
fi
AC_DEFINE_UNQUOTED([PAC_C_MAX_REAL_PRECISION], $PAC_C_MAX_REAL_PRECISION, [Determine the maximum decimal precision in C])
AC_MSG_RESULT([$PAC_C_MAX_REAL_PRECISION])
2016-01-28 05:45:23 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if they would like the Fortran interface compiled
##
2016-01-28 05:45:23 +08:00
## This needs to be exposed for the library info file even if Fortran is disabled.
AC_SUBST([HDF_FORTRAN])
## Default is no Fortran
HDF_FORTRAN=no
2003-07-29 05:38:04 +08:00
AC_SUBST([HDF5_INTERFACES]) HDF5_INTERFACES=""
AC_MSG_CHECKING([if Fortran interface enabled])
2002-07-18 00:10:46 +08:00
AC_ARG_ENABLE([fortran],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-fortran],
2015-08-11 22:35:30 +08:00
[Compile the Fortran interface [default=no]])],
2002-07-18 00:10:46 +08:00
[HDF_FORTRAN=$enableval])
2000-09-08 04:57:34 +08:00
2011-08-21 11:17:37 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
echo "yes"
else
echo "no"
fi
2000-09-15 06:19:24 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
2003-07-29 05:38:04 +08:00
2016-03-01 22:50:49 +08:00
## We will output an include file for Fortran, H5config_f.inc which
## contains various configure definitions used by the Fortran Library.
## Prepend H5_ to all macro names. This avoids name conflict between HDF5 macro
2015-08-11 22:35:30 +08:00
## names and those generated by another software package that uses the HDF5 library.
2016-03-01 22:50:49 +08:00
AC_CONFIG_HEADERS([fortran/src/H5config_f.inc],
2015-08-11 22:35:30 +08:00
[cat fortran/src/H5config_f.inc | sed '1d;s%^/\* \(.*\) \*/%\1%;s/#define /#define H5_/;s/#undef /#undef H5_/' >fortran/src/H5config_f.inc.tmp; mv -f fortran/src/H5config_f.inc.tmp fortran/src/H5config_f.inc])
2016-01-28 05:45:23 +08:00
AC_SUBST([FC])
2015-06-17 05:25:03 +08:00
2003-07-29 05:38:04 +08:00
HDF5_INTERFACES="$HDF5_INTERFACES fortran"
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------
## HDF5 integer variables for the H5fortran_types.f90 file.
##
2003-07-29 05:38:04 +08:00
AC_SUBST([R_LARGE])
AC_SUBST([R_INTEGER])
2005-01-11 06:56:20 +08:00
AC_SUBST([HADDR_T])
2003-07-29 05:38:04 +08:00
AC_SUBST([HSIZE_T])
AC_SUBST([HSSIZE_T])
AC_SUBST([HID_T])
AC_SUBST([SIZE_T])
AC_SUBST([OBJECT_NAMELEN_DEFAULT_F])
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------
## Fortran source extention
##
2006-11-11 03:56:04 +08:00
AC_FC_SRCEXT([f90])
2005-03-11 04:52:34 +08:00
2003-07-29 05:38:04 +08:00
AC_SUBST([F9XSUFFIXFLAG])
AC_SUBST([FSEARCH_DIRS])
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------
2015-02-17 01:17:49 +08:00
## Check for a Fortran compiler and how to include modules.
2015-06-17 05:25:03 +08:00
##
2015-02-17 01:17:49 +08:00
AC_PROG_FC([PAC_FC_SEARCH_LIST],)
2003-07-29 05:38:04 +08:00
AC_F9X_MODS
2012-09-12 04:11:44 +08:00
## Change to the Fortran 90 language
2005-03-11 04:52:34 +08:00
AC_LANG_PUSH(Fortran)
2003-07-29 05:38:04 +08:00
2015-08-11 22:35:30 +08:00
## Checking if the compiler supports the required Fortran 2003 features and
## stopping if it does not.
PAC_PROG_FC_HAVE_F2003_REQUIREMENTS
2016-03-01 22:50:49 +08:00
2015-08-11 22:35:30 +08:00
if test "X$HAVE_F2003_REQUIREMENTS" = "Xno"; then
AC_MSG_ERROR([Fortran compiler lacks required Fortran 2003 features; unsupported Fortran 2003 compiler, remove --enable-fortran])
fi
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------
## Define wrappers for the C compiler to use Fortran function names
##
2005-04-05 05:17:51 +08:00
AC_FC_WRAPPERS
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------
## See if the fortran compiler supports the intrinsic function "SIZEOF"
2015-02-17 01:17:49 +08:00
PAC_PROG_FC_SIZEOF
2008-09-02 23:04:59 +08:00
2014-06-16 23:33:06 +08:00
## See if the fortran compiler supports the intrinsic function "C_SIZEOF"
2015-02-17 01:17:49 +08:00
PAC_PROG_FC_C_SIZEOF
2016-03-01 22:50:49 +08:00
2014-06-16 23:33:06 +08:00
## See if the fortran compiler supports the intrinsic function "STORAGE_SIZE"
2015-06-17 05:25:03 +08:00
PAC_PROG_FC_STORAGE_SIZE
2014-06-16 23:33:06 +08:00
2015-08-11 22:35:30 +08:00
## Set the sizeof function for use later in the fortran tests
if test "X$HAVE_STORAGE_SIZE_FORTRAN" = "Xyes";then
FC_SIZEOF_A="STORAGE_SIZE(a, c_size_t)/STORAGE_SIZE(c_char_'a',c_size_t)"
FC_SIZEOF_B="STORAGE_SIZE(b, c_size_t)/STORAGE_SIZE(c_char_'a',c_size_t)"
FC_SIZEOF_C="STORAGE_SIZE(c, c_size_t)/STORAGE_SIZE(c_char_'a',c_size_t)"
2016-03-01 22:50:49 +08:00
else
2015-08-11 22:35:30 +08:00
if test "X$HAVE_SIZEOF_FORTRAN" = "Xyes";then
FC_SIZEOF_A="SIZEOF(a)"
FC_SIZEOF_B="SIZEOF(b)"
FC_SIZEOF_C="SIZEOF(c)"
2016-03-01 22:50:49 +08:00
else
2015-08-11 22:35:30 +08:00
## If neither intrinsic functions SIZEOF or STORAGE_SIZE is available then stop configure with an error
AC_MSG_ERROR([Fortran compiler requires either intrinsic functions SIZEOF or STORAGE_SIZE])
fi
fi
2011-08-18 22:32:47 +08:00
2015-08-11 22:35:30 +08:00
## See if the fortran compiler supports the intrinsic module "ISO_FORTRAN_ENV"
PAC_PROG_FC_ISO_FORTRAN_ENV
## Check KIND and size of native integer
PAC_FC_NATIVE_INTEGER
2016-03-01 22:50:49 +08:00
2015-08-11 22:35:30 +08:00
## Find all available KINDs
PAC_FC_AVAIL_KINDS
## Find all sizeofs for available KINDs
PAC_FC_SIZEOF_INT_KINDS
PAC_FC_SIZEOF_REAL_KINDS
AC_SUBST([PAC_FC_ALL_REAL_KINDS])
AC_SUBST([PAC_FC_MAX_REAL_PRECISION])
2016-09-27 02:27:50 +08:00
AC_SUBST([PAC_FORTRAN_NUM_INTEGER_KINDS])
2015-08-11 22:35:30 +08:00
AC_SUBST([PAC_FC_ALL_INTEGER_KINDS])
AC_SUBST([PAC_FC_ALL_REAL_KINDS_SIZEOF])
2016-03-01 22:50:49 +08:00
AC_SUBST([PAC_FC_ALL_INTEGER_KINDS_SIZEOF])
2015-08-11 22:35:30 +08:00
AC_SUBST([PAC_FORTRAN_NATIVE_INTEGER_KIND])
AC_SUBST([PAC_FORTRAN_NATIVE_INTEGER_SIZEOF])
AC_SUBST([PAC_FORTRAN_NATIVE_REAL_KIND])
AC_SUBST([PAC_FORTRAN_NATIVE_REAL_SIZEOF])
AC_SUBST([PAC_FORTRAN_NATIVE_DOUBLE_KIND])
AC_SUBST([PAC_FORTRAN_NATIVE_DOUBLE_SIZEOF])
AC_SUBST([HAVE_Fortran_INTEGER_SIZEOF_16])
AC_SUBST([FORTRAN_HAVE_C_LONG_DOUBLE])
AC_SUBST([FORTRAN_C_LONG_DOUBLE_IS_UNIQUE])
AC_SUBST([FORTRAN_SIZEOF_LONG_DOUBLE])
AC_SUBST([H5CONFIG_F_NUM_RKIND])
2016-03-01 22:50:49 +08:00
AC_SUBST([H5CONFIG_F_RKIND])
AC_SUBST([H5CONFIG_F_RKIND_SIZEOF])
2015-08-11 22:35:30 +08:00
AC_SUBST([H5CONFIG_F_NUM_IKIND])
2015-09-01 02:49:17 +08:00
AC_SUBST([H5CONFIG_F_IKIND])
2016-01-28 05:45:23 +08:00
AC_SUBST([Fortran_COMPILER_ID])
Fortran_COMPILER_ID=none
2015-09-01 02:49:17 +08:00
AC_DEFINE_UNQUOTED([Fortran_COMPILER_ID], $Fortran_COMPILER_ID, [Define Fortran compiler ID])
2015-08-11 22:35:30 +08:00
## Setting definition if there is a 16 byte fortran integer
if `echo $PAC_FC_ALL_INTEGER_KINDS_SIZEOF | grep '16' >/dev/null`; then
2016-03-01 22:50:49 +08:00
HAVE_Fortran_INTEGER_SIZEOF_16="1"
2015-08-11 22:35:30 +08:00
AC_DEFINE([HAVE_Fortran_INTEGER_SIZEOF_16], [1], [Determine if INTEGER*16 is available])
else
HAVE_Fortran_INTEGER_SIZEOF_16="0"
AC_DEFINE([HAVE_Fortran_INTEGER_SIZEOF_16], [0], [Determine if INTEGER*16 is available])
fi
2015-06-10 01:05:09 +08:00
2015-08-11 22:35:30 +08:00
if test "X$HAVE_STORAGE_SIZE_FORTRAN" = "Xyes"; then
AC_DEFINE([FORTRAN_HAVE_STORAGE_SIZE], [1], [Define if we have Fortran intrinsic STORAGE_SIZE])
fi
2015-06-10 01:05:09 +08:00
2017-06-29 08:30:45 +08:00
if test "X$HAVE_C_SIZEOF_FORTRAN" = "Xyes"; then
2015-08-11 22:35:30 +08:00
AC_DEFINE([FORTRAN_HAVE_C_SIZEOF], [1], [Define if we have Fortran intrinsic C_SIZEOF])
fi
2016-03-01 22:50:49 +08:00
2017-06-29 08:30:45 +08:00
if test "X$HAVE_SIZEOF_FORTRAN" = "Xyes"; then
2015-08-11 22:35:30 +08:00
AC_DEFINE([FORTRAN_HAVE_SIZEOF], [1], [Define if we have Fortran intrinsic SIZEOF])
fi
2011-08-18 22:32:47 +08:00
2015-08-11 22:35:30 +08:00
## See if C_LONG_DOUBLE is available
PAC_PROG_FC_HAVE_C_LONG_DOUBLE
2015-06-17 05:25:03 +08:00
2016-03-01 22:50:49 +08:00
FORTRAN_HAVE_C_LONG_DOUBLE="0"
2015-08-11 22:35:30 +08:00
if test "X$HAVE_C_LONG_DOUBLE_FORTRAN" = "Xyes"; then
2016-03-01 22:50:49 +08:00
FORTRAN_HAVE_C_LONG_DOUBLE="1"
2015-08-11 22:35:30 +08:00
AC_DEFINE([FORTRAN_HAVE_C_LONG_DOUBLE], [1], [Define if we have Fortran C_LONG_DOUBLE])
fi
## Is C_LONG_DOUBLE different from C_DOUBLE
FORTRAN_C_LONG_DOUBLE_IS_UNIQUE="0"
2017-06-29 08:30:45 +08:00
if test "$FORTRAN_HAVE_C_LONG_DOUBLE" = "1"; then
2015-08-11 22:35:30 +08:00
PAC_PROG_FC_C_LONG_DOUBLE_EQ_C_DOUBLE
if test "X$C_LONG_DOUBLE_IS_UNIQUE_FORTRAN" = "Xyes"; then
FORTRAN_C_LONG_DOUBLE_IS_UNIQUE="1"
AC_DEFINE([FORTRAN_C_LONG_DOUBLE_IS_UNIQUE], [1], [Define if Fortran C_LONG_DOUBLE is different from C_DOUBLE])
2011-10-12 07:59:40 +08:00
else
2015-08-11 22:35:30 +08:00
FORTRAN_C_LONG_DOUBLE_IS_UNIQUE="0"
fi
fi
2016-03-01 22:50:49 +08:00
2015-08-11 22:35:30 +08:00
FORTRAN_SIZEOF_LONG_DOUBLE=${ac_cv_sizeof_long_double}
AC_DEFINE_UNQUOTED([FORTRAN_SIZEOF_LONG_DOUBLE], ["${ac_cv_sizeof_long_double}"], [Determine the size of C long double])
dnl get the largest sizeof for REAL kinds
2016-05-13 02:36:32 +08:00
max_real_fortran_sizeof="`echo $PAC_FC_ALL_REAL_KINDS_SIZEOF | sed -ne 's/.*,\([[0-9]]*\)}/\1/p'`"
max_real_fortran_kind="`echo $PAC_FC_ALL_REAL_KINDS | sed -ne 's/.*,\([[0-9]]*\)}/\1/p'`"
2015-08-11 22:35:30 +08:00
dnl remove the invalid kind from the list
if test "$ac_cv_sizeof___float128" != 0;then
2016-03-01 22:50:49 +08:00
if test "$ac_cv_sizeof___float128" != "$max_real_fortran_sizeof" &&
2015-08-19 06:11:37 +08:00
test "${ac_cv_sizeof_long_double}" != "$max_real_fortran_sizeof" &&
dnl account for the fact that the C compiler can have 16-byte __float128 and the Fortran compiler only has 8-byte doubles,
dnl so we don't want to remove the 8-byte Fortran doubles. This is sometimes the case if different C and Fortran vendors
dnl are used (for example gnu and pgi).
test "${ac_cv_sizeof_double}" != "$max_real_fortran_sizeof" ; then
AC_MSG_WARN([
Fortran REAL(KIND=$max_real_fortran_kind) is $max_real_fortran_sizeof Bytes, but no corresponding C float type exists of that size
!!! Fortran interfaces will not be generated for REAL(KIND=$max_real_fortran_kind) !!!
])
2015-08-18 05:12:03 +08:00
PAC_FC_ALL_REAL_KINDS="`echo $PAC_FC_ALL_REAL_KINDS | sed -e 's/,[[0-9]]\+}/}/g'`"
PAC_FC_ALL_REAL_KINDS_SIZEOF="`echo $PAC_FC_ALL_REAL_KINDS_SIZEOF | sed -e 's/,[[0-9]]\+}/}/g'`"
2016-05-13 02:36:32 +08:00
2011-08-31 10:48:19 +08:00
fi
2011-08-18 22:32:47 +08:00
fi
2015-08-11 22:35:30 +08:00
AC_MSG_CHECKING([for Fortran interoperable KINDS with C])
2016-03-01 22:50:49 +08:00
AC_MSG_RESULT([$PAC_FC_ALL_REAL_KINDS])
2015-08-11 22:35:30 +08:00
dnl count the number of real kinds
2015-08-18 05:12:03 +08:00
H5CONFIG_F_NUM_RKIND="INTEGER, PARAMETER :: num_rkinds = `echo \"[$]PAC_FC_ALL_REAL_KINDS\" | tr -d -c ',\n' | awk '{ print length + 1; }'`"
H5CONFIG_F_RKIND="INTEGER, DIMENSION(1:num_rkinds) :: rkind = (/`echo $PAC_FC_ALL_REAL_KINDS | sed -e 's/{//g' | sed -e 's/}//g' | sed -e 's/ /,/g'`/)"
H5CONFIG_F_RKIND_SIZEOF="INTEGER, DIMENSION(1:num_rkinds) :: rkind_sizeof = (/`echo $PAC_FC_ALL_REAL_KINDS_SIZEOF | sed -e 's/{//g' | sed -e 's/}//g'| sed -e 's/ /,/g'`/)"
2015-08-11 22:35:30 +08:00
AC_DEFINE_UNQUOTED([H5CONFIG_F_NUM_RKIND], $H5CONFIG_F_NUM_RKIND, [Define number of valid Fortran REAL KINDs])
AC_DEFINE_UNQUOTED([H5CONFIG_F_RKIND], $H5CONFIG_F_RKIND, [Define valid Fortran REAL KINDs])
AC_DEFINE_UNQUOTED([H5CONFIG_F_RKIND_SIZEOF], $H5CONFIG_F_RKIND_SIZEOF, [Define valid Fortran REAL KINDs Sizeof])
## Change back to the C language
AC_LANG_POP(Fortran)
2011-11-12 00:04:27 +08:00
else
FC="no"
2000-09-08 04:57:34 +08:00
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if they would like the C++ interface compiled
##
2016-01-28 05:45:23 +08:00
## This needs to be exposed for the library info file even if C++ is disabled.
AC_SUBST([HDF_CXX])
## Default is no C++
HDF_CXX=no
2012-09-12 04:11:44 +08:00
## We need to check for a C++ compiler unconditionally, since
## AC_PROG_CXX defines some macros that Automake 1.9.x uses and will
## miss even if c++ is not enabled.
2016-01-28 05:45:23 +08:00
AC_PROG_CXX
2016-03-01 22:50:49 +08:00
AC_PROG_CXXCPP ## this is checked for when AC_HEADER_STDC is done
[svn-r10158] Purpose:
Automake version upgrade
Description:
Upgraded automake version from 1.6.2 to 1.9.5.
Changed bin/reconfigure script to use automake 1.9.5.
Changed configure.in and Makefiles to use new FCFLAGS and FC variables
instead of FFLAGS and F9X.
Automake and configure should now do the lion's share of the work
supporting Fortran 9X; macros in acsite.m4 are now mostly unused (will
be cleaned later).
Altered how configure handles pmake; now root-level Makefile.in is
processed by bin/reconfigure to have a .MAKEFLAGS target, since
automake no longer allows us to define unused variables.
Configure now always checks for C++ compiler even if it is not
used, since automake thinks this is the Right Thing To Do and
will break otherwise.
Platforms tested:
Sol, copper, heping, mir, sleipnir, eirene, pommier, kelgia, modi4.
2005-03-08 01:57:27 +08:00
2006-06-15 04:16:27 +08:00
AC_MSG_CHECKING([if c++ interface enabled])
2002-07-18 00:10:46 +08:00
AC_ARG_ENABLE([cxx],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-cxx],
2002-07-18 00:10:46 +08:00
[Compile the C++ interface [default=no]])],
[HDF_CXX=$enableval])
2000-09-08 04:57:34 +08:00
2000-09-15 06:19:24 +08:00
if test "X$HDF_CXX" = "Xyes"; then
2001-08-02 05:00:25 +08:00
echo "yes"
2003-07-29 05:38:04 +08:00
HDF5_INTERFACES="$HDF5_INTERFACES c++"
2016-01-28 05:45:23 +08:00
## Expose the compiler for *.in files
AC_SUBST([CXX])
2012-09-12 04:11:44 +08:00
## Change to the C++ language
2005-03-11 04:52:34 +08:00
AC_LANG_PUSH(C++)
2003-07-29 05:38:04 +08:00
2016-01-28 05:45:23 +08:00
## Checking if C++ needs old style header files in includes
2015-02-17 01:17:49 +08:00
PAC_PROG_CXX_HEADERS
2003-07-29 05:38:04 +08:00
2016-01-28 05:45:23 +08:00
## Checking if C++ can handle namespaces
2015-02-17 01:17:49 +08:00
PAC_PROG_CXX_NAMESPACE
2015-06-17 05:25:03 +08:00
2016-01-28 05:45:23 +08:00
## if C++ can handle static cast
2015-02-17 01:17:49 +08:00
PAC_PROG_CXX_STATIC_CAST
2003-07-29 05:38:04 +08:00
2016-11-03 23:58:43 +08:00
## Checking if C++ has offsetof extension,
2016-07-21 00:10:42 +08:00
## note: this test has to be the last of the C++ tests because it sets a definition
## which would be used in the other tests, causing them to fail.
PAC_PROG_CXX_OFFSETOF
2015-02-17 01:17:49 +08:00
else
AC_MSG_RESULT([no])
CXX="no"
fi
2003-07-29 05:38:04 +08:00
2015-02-17 01:17:49 +08:00
## Change back to the C language
AC_LANG_POP(C++)
2003-07-29 05:38:04 +08:00
2015-02-17 01:17:49 +08:00
## ----------------------------------------------------------------------
## Check if they would like the High Level library compiled
##
2003-07-29 05:38:04 +08:00
2016-01-28 05:45:23 +08:00
## This needs to be exposed for the library info file even if the HL
## library is disabled.
AC_SUBST([HDF5_HL])
## The high-level library is enabled unless the build mode is clean.
if test "X-$BUILD_MODE" = "X-clean" ; then
HDF5_HL=no
else
HDF5_HL=yes
fi
## high-level library directories (set when needed, blank until then)
##
## main high-level library
AC_SUBST(HL)
HL=""
## Fortran high-level library
AC_SUBST(HL_FOR)
HL_FOR=""
AC_MSG_CHECKING([if the high-level library is enabled])
2015-02-17 01:17:49 +08:00
AC_ARG_ENABLE([hl],
[AS_HELP_STRING([--enable-hl],
2016-01-28 05:45:23 +08:00
[Enable the high-level library.
[default=yes (unless build mode = clean)]
])],
[HDF5_HL=$enableval])
2015-02-17 01:17:49 +08:00
2016-01-28 05:45:23 +08:00
if test "X-$HDF5_HL" = "X-yes"; then
AC_MSG_RESULT([yes])
2015-02-17 01:17:49 +08:00
HL="hl"
AC_DEFINE([INCLUDE_HL], [1],
2016-01-28 05:45:23 +08:00
[Define if the high-level library headers should be included in hdf5.h])
2000-09-08 04:57:34 +08:00
else
2016-01-28 05:45:23 +08:00
AC_MSG_RESULT([no])
2000-09-08 04:57:34 +08:00
fi
2006-06-15 04:16:27 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check which archiving tool to use. This needs to be done before
## the AM_PROG_LIBTOOL macro.
##
2012-06-05 01:05:02 +08:00
2000-09-26 01:35:08 +08:00
if test -z "$AR"; then
2002-07-18 00:10:46 +08:00
AC_CHECK_PROGS([AR], [ar xar], [:], [$PATH])
1998-03-06 13:34:36 +08:00
fi
2002-07-18 00:10:46 +08:00
AC_SUBST([AR])
1998-03-06 13:34:36 +08:00
2012-09-12 04:11:44 +08:00
## Export the AR macro so that it will be placed in the libtool file
## correctly.
2000-09-26 01:35:08 +08:00
export AR
2004-12-29 22:26:20 +08:00
AC_PROG_MAKE_SET
AC_PROG_INSTALL
[svn-r11411] Purpose:
Bug fix
Description:
Building with --disable-static seems to have been broken on several platforms.
Fixed this.
Configure will now disable shared libraries automatically when using pgf90
or when building on Cygwin.
Solution:
To avoid errors when using shared libraries with pgf90 (which I had not
realized were compiler-specific), I had manually set convenience libraries
to use the -static linking flag. Apparently, this is not necessary, and
caused these libraries to be created as empty archives when --disable-static
was used.
Also, some libraries were including other libraries, which was not
necessary.
I also fixed code in configure.in to correctly detect whether shared
or static libraries are enabled, and moved code that disables shared libraries
to before libtool is created (rather than editing libtool after the fact).
Despite repeated warnings that only one shared library can be linked at a
time, I have yet to have shared libraries break the linking of tests on
any system. We'll see if the Daily Tests turn up anything.
Platforms tested:
mir (fortran, C++), sleipnir (C++), modi4 (fortran, C++, parallel),
sol (fortran, C++), cygwin
2005-09-14 06:30:33 +08:00
2006-06-15 04:16:27 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2016-01-28 05:45:23 +08:00
## Set up ${TR} which is used to process the package list for extra
## debugging output in the C library.
2015-03-31 02:55:21 +08:00
2012-09-12 04:11:44 +08:00
AC_PATH_PROG([TR], [tr])
2006-10-04 06:41:34 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check that time can be used with srcdir. This is okay on most systems,
## but seems to cause problems on Cygwin.
## The solution on Cygwin is not to record execution time for tests.
2015-02-19 05:06:47 +08:00
##
## Note: This is still true as of Cygwin 1.7.32 (Aug 2014) on both 32-
## and 64-bit platforms. Given how long this has been true, it seems
## unlikely to change, but we should probably re-test this periodically.
2007-01-24 01:29:45 +08:00
AC_MSG_CHECKING([if srcdir= and time commands work together])
AC_SUBST([TIME])
TIME=time
2007-01-25 23:30:53 +08:00
TIME_TEST=`foo="bar" ${TIME} echo 'baz' 2> /dev/null | grep baz`
2007-01-24 01:29:45 +08:00
if test "X${TIME_TEST}" = "Xbaz"; then
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
TIME=
fi
2012-09-12 04:11:44 +08:00
## The following variables are used to distinguish between building a
## serial and parallel library.
##
2016-03-01 22:50:49 +08:00
## HAVE_PARALLEL -- defined in H5config.h if we are building
## a parallel library even if configure wasn't
## able to find some header file or library that
## might be required. This is defined if the
## user explicitly states
## that a parallel library is being built by supplying
## the `--enable-parallel' configure switch.
##
## PARALLEL -- This variable is set to a non-null value if
## we're building a parallel version of the library.
##
## RUNSERIAL -- This is a command which will be prepended to
## the executable name to run the executable using
## a single process. For serial versions of the
## library this will normally be empty. For parallel
## versions it might be something like `mpiexec -n 1'.
## The value of this variable is substituted in *.in
## files.
##
## RUNPARALLEL -- This is a command which will be prepended to
## the executable name to run the executable on
## multiple processors. For the serial library the
## value will normally be the empty string. For
## parallel library it should be something like
## "mpiexec -n \$\${NPROCS:=6}" where NPROCS will
## eventually contain the number of processors on which
## to run the executable (the double dollarsigns are to
## protect the expansion until make executes the
## command). The value of this variable is
## substituted in *.in files.
2012-09-12 04:11:44 +08:00
##
2006-06-15 04:16:27 +08:00
AC_SUBST([PARALLEL])
AC_SUBST([RUNSERIAL])
AC_SUBST([RUNPARALLEL])
AC_SUBST([TESTPARALLEL])
2015-04-18 06:24:47 +08:00
## ----------------------------------------------------------------------
## Disable shared libraries on CYGWIN. (LK - 04/16/15)
## A number of tests run by "make check" fail on CYGWIN, so for HDF5 v1.8.15
## we will change the default for shared libraries to disabled.
case "`uname`" in
CYGWIN*)
enable_shared="no"
CHECK_WARN="Shared libraries are not currently supported on CYGWIN."
;;
esac
2016-02-29 10:43:00 +08:00
## ----------------------------------------------------------------------
## Check if they would like the Java native interface (JNI) compiled
##
2016-03-22 15:22:52 +08:00
## This needs to be exposed for the library info file even if Java is disabled.
2016-03-01 23:25:56 +08:00
AC_SUBST([HDF_JAVA])
2016-03-22 15:22:52 +08:00
## Default is no Java
2016-03-02 00:00:56 +08:00
HDF_JAVA=no
2016-02-29 10:43:00 +08:00
AC_SUBST([H5_CLASSPATH]) H5_CLASSPATH=""
AC_MSG_CHECKING([if Java JNI interface enabled])
AC_ARG_ENABLE([java],
[AS_HELP_STRING([--enable-java],
[Compile the Java JNI interface [default=no]])],
2016-03-02 00:00:56 +08:00
[HDF_JAVA=$enableval])
2016-02-29 10:43:00 +08:00
2016-03-01 23:04:39 +08:00
if test "X$HDF_JAVA" = "Xyes"; then
2016-03-01 22:50:49 +08:00
if test "X${enable_shared}" != "Xno"; then
echo "yes"
if test "X$CLASSPATH" = "X"; then
H5_CLASSPATH=".:$srcdir/java/lib"
else
H5_CLASSPATH=".:$CLASSPATH:$srcdir/java/lib"
fi
## Checks for programs.
AX_JAVA_OPTIONS
H5_JAVACFLAGS=$JAVACFLAGS
H5_JAVAFLAGS=$JAVAFLAGS
AX_PROG_JAVAC
AX_PROG_JAVA
AX_PROG_JAR
AX_PROG_JAVADOC
## Find the include directories needed for building JNI code
AX_JNI_INCLUDE_DIR()
for JNI_INCLUDE_DIR in $JNI_INCLUDE_DIRS
do
JNIFLAGS="$JNIFLAGS -I$JNI_INCLUDE_DIR"
done
## Find junit for testing the JNI code
AX_CHECK_CLASSPATH()
CLASSPATH_ENV=$H5_CLASSPATH
AX_CHECK_JUNIT()
AX_CHECK_JAVA_HOME
2016-02-29 10:43:00 +08:00
2016-03-01 22:50:49 +08:00
AC_MSG_RESULT([yes])
else
2016-02-29 10:43:00 +08:00
AC_MSG_ERROR([Java requires shared libraries to be built])
2016-03-02 01:54:56 +08:00
HDF_JAVA="no"
AC_MSG_RESULT([no])
2016-02-29 10:43:00 +08:00
fi
2016-03-02 01:54:56 +08:00
else
2016-02-29 10:43:00 +08:00
AC_MSG_RESULT([no])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2015-03-21 05:48:41 +08:00
## Fortran libraries are not currently supported on Mac. Disable them.
## (this is overridable with --enable-unsupported).
2012-09-12 04:11:44 +08:00
##
[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
AC_SUBST([H5_FORTRAN_SHARED])
H5_FORTRAN_SHARED="no"
if test "X${HDF_FORTRAN}" = "Xyes" && test "X${enable_shared}" != "Xno"; then
AC_MSG_CHECKING([if shared Fortran libraries are supported])
2005-09-16 05:30:06 +08:00
H5_FORTRAN_SHARED="yes"
2017-05-23 22:53:59 +08:00
## tell libtool to do the right thing with COMMON symbols, this fixes
## corrupt values with COMMON and EQUIVALENCE when building shared
## Fortran libraries on OSX with gnu and Intel compilers (HDFFV-2772).
2015-03-21 05:48:41 +08:00
case "`uname`" in
Darwin*)
2017-05-19 05:32:26 +08:00
H5_LDFLAGS="$H5_LDFLAGS -Wl,-commons,use_dylibs"
2017-05-23 22:53:59 +08:00
;;
2015-03-21 05:48:41 +08:00
esac
## Report results of check(s)
2015-06-17 05:25:03 +08:00
2015-03-21 05:48:41 +08:00
if test "X${H5_FORTRAN_SHARED}" = "Xno"; then
AC_MSG_RESULT([no])
AC_MSG_WARN([$CHECK_WARN])
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
AC_MSG_WARN([Disabling shared Fortran libraries.])
AC_MSG_WARN([To override this behavior, please use --enable-unsupported configure option.])
if test "X${enable_static}" = "Xno"; then
AC_MSG_ERROR([both static and shared Fortran libraries are disabled])
fi
else
AC_MSG_WARN([Allowing unsupported Fortran shared libraries due to use of --enable-unsupported flag])
H5_FORTRAN_SHARED="yes"
fi
else
AC_MSG_RESULT([yes])
fi
[svn-r11411] Purpose:
Bug fix
Description:
Building with --disable-static seems to have been broken on several platforms.
Fixed this.
Configure will now disable shared libraries automatically when using pgf90
or when building on Cygwin.
Solution:
To avoid errors when using shared libraries with pgf90 (which I had not
realized were compiler-specific), I had manually set convenience libraries
to use the -static linking flag. Apparently, this is not necessary, and
caused these libraries to be created as empty archives when --disable-static
was used.
Also, some libraries were including other libraries, which was not
necessary.
I also fixed code in configure.in to correctly detect whether shared
or static libraries are enabled, and moved code that disables shared libraries
to before libtool is created (rather than editing libtool after the fact).
Despite repeated warnings that only one shared library can be linked at a
time, I have yet to have shared libraries break the linking of tests on
any system. We'll see if the Daily Tests turn up anything.
Platforms tested:
mir (fortran, C++), sleipnir (C++), modi4 (fortran, C++, parallel),
sol (fortran, C++), cygwin
2005-09-14 06:30:33 +08:00
fi
2015-03-21 05:48:41 +08:00
2005-09-16 05:30:06 +08:00
AM_CONDITIONAL([FORTRAN_SHARED_CONDITIONAL], [test "X$H5_FORTRAN_SHARED" = "Xyes"])
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Create libtool. If shared/static libraries are going to be enabled
## or disabled, it should happen before these macros.
2012-09-18 00:10:12 +08:00
LT_PREREQ([2.2])
2015-03-31 02:55:21 +08:00
## ----------------------------------------------------------------------
## dlopen - This will use an improved version of libtool
## win32-dll - This will build clean dlls on win32 platforms.
LT_INIT([dlopen,win32-dll])
2004-12-29 22:26:20 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if we should install only statically linked executables.
## This check needs to occur after libtool is initialized because
2015-06-17 05:25:03 +08:00
## we check a libtool cache value and may issue a warning based
2012-09-12 04:11:44 +08:00
## on its result.
2016-01-28 05:45:23 +08:00
AC_SUBST([STATIC_EXEC])
## Default is no
STATIC_EXEC=no
2009-09-01 00:21:56 +08:00
AC_MSG_CHECKING([if we should install only statically linked executables])
AC_ARG_ENABLE([static_exec],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-static-exec],
2009-09-01 00:21:56 +08:00
[Install only statically linked executables
[default=no]])],
[STATIC_EXEC=$enableval])
if test "X$STATIC_EXEC" = "Xyes"; then
echo "yes"
2012-09-12 04:11:44 +08:00
## Issue a warning if -static flag is not supported.
2009-09-01 00:21:56 +08:00
if test "X$lt_cv_prog_compiler_static_works" = "Xno"; then
2016-01-28 05:45:23 +08:00
echo " warning: -static flag not supported on this system; executable won't statically link shared system libraries."
LT_STATIC_EXEC=""
2013-09-10 22:24:34 +08:00
else
LT_STATIC_EXEC="-all-static"
2009-09-01 00:21:56 +08:00
fi
else
echo "no"
LT_STATIC_EXEC=""
fi
2013-09-10 22:24:34 +08:00
AM_CONDITIONAL([USE_PLUGINS_CONDITIONAL], [test "X$LT_STATIC_EXEC" = X])
2009-09-01 00:21:56 +08:00
AC_SUBST([LT_STATIC_EXEC])
2012-09-12 04:11:44 +08:00
## Fix up the INSTALL macro if it's a relative path. We want the
## full-path to the binary instead.
2001-02-13 06:52:00 +08:00
case "$INSTALL" in
2001-08-02 05:00:25 +08:00
*install-sh*)
INSTALL='\${top_srcdir}/bin/install-sh -c'
;;
2001-02-13 06:52:00 +08:00
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Some users have reported problems with libtool's use of '-Wl,-rpath' to
## link shared libraries in nondefault directories. Allow users to
## disable embedding the rpath information in the executables and to
## instead solely rely on the information in LD_LIBRARY_PATH.
2008-05-16 05:08:23 +08:00
AC_MSG_CHECKING([if -Wl,-rpath should be used to link shared libs in nondefault directories])
AC_ARG_ENABLE([sharedlib-rpath],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--disable-sharedlib-rpath],
2008-05-16 05:08:23 +08:00
[Disable use of the '=Wl,-rpath' linker option])],
[RPATH=$enableval])
case "X-$RPATH" in
X-no)
AC_MSG_RESULT([no])
2008-05-31 05:47:44 +08:00
runpath_var=
hardcode_libdir_flag_spec=
hardcode_libdir_flag_spec_ld=
2014-04-26 05:59:53 +08:00
hardcode_into_libs=no
2008-05-16 05:08:23 +08:00
;;
X-|X-yes)
AC_MSG_RESULT([yes])
;;
*)
AC_MSG_RESULT([error])
AC_MSG_ERROR([\'$enableval\' is not a valid rpath type])
;;
esac
1999-11-01 23:21:16 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2013-03-14 03:35:26 +08:00
## Check for system libraries. "dl" stands for dynamically loaded library
2012-09-12 04:11:44 +08:00
##
2002-07-18 00:10:46 +08:00
AC_CHECK_LIB([m], [ceil])
2013-03-14 03:35:26 +08:00
AC_CHECK_LIB([dl], [dlopen])
2001-07-06 04:56:01 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check for system header files.
##
1997-08-16 00:35:53 +08:00
AC_HEADER_STDC
1998-11-03 01:58:28 +08:00
AC_HEADER_TIME
2002-07-18 00:10:46 +08:00
2012-09-12 04:11:44 +08:00
## Unix
2002-07-18 00:10:46 +08:00
AC_CHECK_HEADERS([sys/resource.h sys/time.h unistd.h sys/ioctl.h sys/stat.h])
2015-12-11 16:19:10 +08:00
AC_CHECK_HEADERS([sys/socket.h sys/types.h sys/file.h])
2002-07-18 00:10:46 +08:00
AC_CHECK_HEADERS([stddef.h setjmp.h features.h])
2013-03-19 11:00:40 +08:00
AC_CHECK_HEADERS([dirent.h])
2002-07-18 00:10:46 +08:00
AC_CHECK_HEADERS([stdint.h], [C9x=yes])
2015-10-20 14:28:17 +08:00
AC_CHECK_HEADERS([stdbool.h])
2002-07-18 00:10:46 +08:00
2012-09-12 04:11:44 +08:00
## Darwin
2011-05-24 01:29:14 +08:00
AC_CHECK_HEADERS([mach/mach_time.h])
2012-12-20 05:51:55 +08:00
## Also need to detect Darwin for pubconf
case $host_os in
darwin*)
AC_DEFINE([HAVE_DARWIN], [1], [Define if Darwin or Mac OS X])
;;
esac
2011-05-24 01:29:14 +08:00
2012-09-12 04:11:44 +08:00
## Windows
2005-09-02 04:38:18 +08:00
case "`uname`" in
CYGWIN*)
AC_CHECK_HEADERS([io.h sys/timeb.h])
;;
2012-06-19 04:01:59 +08:00
MINGW*)
AC_CHECK_HEADERS([io.h winsock2.h sys/timeb.h])
AC_HAVE_LIBRARY([ws2_32])
;;
2005-09-02 04:38:18 +08:00
*)
2012-06-05 01:05:02 +08:00
AC_CHECK_HEADERS([io.h winsock2.h sys/timeb.h])
2005-09-02 04:38:18 +08:00
;;
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Some platforms require that all symbols are resolved when a library
## is linked. We can use the -no-undefined flag to tell libtool that
## it will be able to build shared libraries on these architectures,
## as it will not do so by default.
##
2011-04-15 05:21:59 +08:00
if test "X${enable_shared}" = "Xyes"; then
AC_MSG_CHECKING([if libtool needs -no-undefined flag to build shared libraries])
case "`uname`" in
CYGWIN*|MINGW*|AIX*)
2012-09-12 04:11:44 +08:00
## Add in the -no-undefined flag to LDFLAGS for libtool.
2011-04-15 05:21:59 +08:00
AC_MSG_RESULT([yes])
H5_LDFLAGS="$H5_LDFLAGS -no-undefined"
;;
*)
2012-09-12 04:11:44 +08:00
## Don't add in anything.
2011-04-15 05:21:59 +08:00
AC_MSG_RESULT([no])
;;
esac
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2015-02-17 00:17:03 +08:00
## Use the macro _AC_SYS_LARGEFILE_MACRO_VALUE to test defines
2015-06-17 05:25:03 +08:00
## that might need to be set for largefile support to behave
2015-02-17 00:17:03 +08:00
## correctly. This macro is defined in acsite.m4 and overrides
## the version provided by Autoconf (as of v2.65). The custom
2015-06-17 05:25:03 +08:00
## macro additionally adds the appropriate defines to AM_CPPFLAGS
## so that later configure checks have them visible.
2015-02-17 00:17:03 +08:00
## Check for _FILE_OFFSET_BITS
_AC_SYS_LARGEFILE_MACRO_VALUE([_FILE_OFFSET_BITS], [64],
[ac_cv_sys_file_offset_bits],
[Number of bits in a file offset, on hosts where this is settable.],
[_AC_SYS_LARGEFILE_TEST_INCLUDES])
## Check for _LARGE_FILES
if test "$ac_cv_sys_file_offset_bits" = unknown; then
_AC_SYS_LARGEFILE_MACRO_VALUE([_LARGE_FILES], [1],
[ac_cv_sys_large_files],
[Define for large files, on AIX-style hosts.],
2010-05-06 01:34:26 +08:00
[_AC_SYS_LARGEFILE_TEST_INCLUDES])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Add necessary defines for Linux Systems.
##
2001-05-09 04:59:31 +08:00
case "$host_cpu-$host_vendor-$host_os" in
2001-09-28 07:05:16 +08:00
*linux*)
2012-09-12 04:11:44 +08:00
## Add POSIX support on Linux systems, so <features.h> defines
## __USE_POSIX, which is required to get the prototype for fdopen
2015-06-17 05:25:03 +08:00
## defined correctly in <stdio.h>.
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
##
2012-09-12 04:11:44 +08:00
## This flag was removed from h5cc as of 2009-10-17 when it was found
2015-06-17 05:25:03 +08:00
## that the flag broke compiling netCDF-4 code with h5cc, but kept in
2012-09-12 04:11:44 +08:00
## H5_CPPFLAGS because fdopen and HDfdopen fail without it. HDfdopen
## is used only by H5_debug_mask which is used only when debugging in
## H5_init_library (all in H5.c). When the flag was removed this was
## the only compile failure noted.
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
##
2012-09-12 04:11:44 +08:00
## This was originally defined as _POSIX_SOURCE which was updated to
## _POSIX_C_SOURCE=199506L to expose a greater amount of POSIX
## functionality so clock_gettime and CLOCK_MONOTONIC are defined
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
## correctly. This was later updated to 200112L so that
## posix_memalign() is visible for the direct VFD code on Linux
## systems.
##
2012-09-12 04:11:44 +08:00
## POSIX feature information can be found in the gcc manual at:
## http://www.gnu.org/s/libc/manual/html_node/Feature-Test-Macros.html
2015-09-05 21:51:10 +08:00
H5_CPPFLAGS="-D_POSIX_C_SOURCE=200112L $H5_CPPFLAGS"
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
## Need to add this so that O_DIRECT is visible for the direct
## VFD on Linux systems.
2015-03-04 06:27:21 +08:00
H5_CPPFLAGS="-D_GNU_SOURCE $H5_CPPFLAGS"
2001-09-28 07:05:16 +08:00
;;
2001-05-09 04:59:31 +08:00
esac
2015-06-17 05:25:03 +08:00
## Need to add the AM_ and H5_ into CFLAGS/CPPFLAGS to make them visible
2012-09-12 04:11:44 +08:00
## for configure checks.
## Note: Both will be restored by the end of configure.
2011-05-24 01:02:39 +08:00
CPPFLAGS="$H5_CPPFLAGS $AM_CPPFLAGS $CPPFLAGS"
CFLAGS="$H5_CFLAGS $AM_CFLAGS $CFLAGS"
[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
2012-09-12 04:11:44 +08:00
## Checkpoint the cache
2000-04-21 02:41:51 +08:00
AC_CACHE_SAVE
2012-09-12 04:11:44 +08:00
## Posix.1g types (C9x)
1998-11-19 02:40:09 +08:00
cat >>confdefs.h <<\EOF
#include <sys/types.h>
EOF
2000-09-15 06:19:24 +08:00
if test "X$C9x" = "Xyes"; then
2001-09-28 07:05:16 +08:00
cat >>confdefs.h <<\EOF
1999-08-21 01:05:14 +08:00
#include <stdint.h>
EOF
fi
2015-12-03 10:45:08 +08:00
AC_CHECK_SIZEOF( [int8_t])
AC_CHECK_SIZEOF( [uint8_t])
AC_CHECK_SIZEOF( [int_least8_t])
AC_CHECK_SIZEOF( [uint_least8_t])
AC_CHECK_SIZEOF( [int_fast8_t])
AC_CHECK_SIZEOF( [uint_fast8_t])
AC_CHECK_SIZEOF( [int16_t])
AC_CHECK_SIZEOF( [uint16_t])
AC_CHECK_SIZEOF( [int_least16_t])
AC_CHECK_SIZEOF([uint_least16_t])
AC_CHECK_SIZEOF( [int_fast16_t])
AC_CHECK_SIZEOF( [uint_fast16_t])
AC_CHECK_SIZEOF( [int32_t])
AC_CHECK_SIZEOF( [uint32_t])
AC_CHECK_SIZEOF( [int_least32_t])
AC_CHECK_SIZEOF([uint_least32_t])
AC_CHECK_SIZEOF( [int_fast32_t])
AC_CHECK_SIZEOF( [uint_fast32_t])
AC_CHECK_SIZEOF( [int64_t])
AC_CHECK_SIZEOF( [uint64_t])
AC_CHECK_SIZEOF( [int_least64_t])
AC_CHECK_SIZEOF([uint_least64_t])
AC_CHECK_SIZEOF( [int_fast64_t])
AC_CHECK_SIZEOF( [uint_fast64_t])
AC_CHECK_SIZEOF([size_t])
AC_CHECK_SIZEOF([ssize_t])
AC_CHECK_SIZEOF([ptrdiff_t])
2002-07-18 00:10:46 +08:00
1998-03-06 05:27:38 +08:00
cat >>confdefs.h <<\EOF
#include <sys/types.h> /*for off_t definition*/
EOF
2015-12-03 10:45:08 +08:00
AC_CHECK_SIZEOF([off_t])
1997-08-16 00:35:53 +08:00
2015-10-20 14:28:17 +08:00
if test "X$C9x" = "Xyes"; then
cat >>confdefs.h <<\EOF
#ifdef HAVE_STDBOOL_H
#include <stdbool.h> /* for bool definition */
#else
#define bool _Bool
#endif
EOF
2015-12-03 10:45:08 +08:00
AC_CHECK_SIZEOF([bool])
2015-10-20 14:28:17 +08:00
fi
2012-09-12 04:11:44 +08:00
## Checkpoint the cache
2000-04-21 02:41:51 +08:00
AC_CACHE_SAVE
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if the dev_t type is a scalar type (must come after the check for
## sys/types.h)
2001-09-28 07:05:16 +08:00
AC_MSG_CHECKING([if dev_t is scalar])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
2001-07-18 05:24:38 +08:00
#ifdef HAVE_SYS_TYPES_H
#include <sys/types.h>
#endif
2015-09-19 20:24:40 +08:00
]],
[[dev_t d1, d2; if(d1==d2) return 0;]])],
[AC_DEFINE([DEV_T_IS_SCALAR], [1],
[Define if dev_t is a scalar])
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
2001-07-18 05:24:38 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Fake --with-xxx option to allow us to create a help message for the
## following --with-xxx options which can take either a =DIR or =INC,LIB
## specifier.
##
2002-07-18 00:10:46 +08:00
AC_ARG_WITH([fnord],
2002-02-14 03:57:10 +08:00
[
For the following --with-xxx options, you can specify where the header
files and libraries are in two different ways:
--with-xxx=INC,LIB - Specify individually the include directory and
library directory separated by a comma
--with-xxx=DIR - Specify only the directory which contains the
include/ and lib/ subdirectories
2002-07-18 00:10:46 +08:00
])
2002-02-14 03:57:10 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2017-06-28 02:35:16 +08:00
## Is dmalloc (debug malloc library) requested? It has a header file
## `dmalloc.h' and a library `-ldmalloc' and their locations might be
## specified with the `--with-dmalloc' command-line switch. The value
## is an include path and/or a library path. If the library path is
## specified then it must be preceded by a comma.
2012-09-12 04:11:44 +08:00
##
2016-01-28 05:45:23 +08:00
AC_SUBST([HAVE_DMALLOC])
## Default is not present
HAVE_DMALLOC=no
2002-07-18 00:10:46 +08:00
AC_ARG_WITH([dmalloc],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--with-dmalloc=DIR],
2002-07-18 00:10:46 +08:00
[Use dmalloc memory debugging aid [default=no]])],,
2012-09-12 04:11:44 +08:00
[withval=no])
2002-07-13 02:29:41 +08:00
case $withval in
yes)
HAVE_DMALLOC="yes"
2013-03-14 06:34:23 +08:00
AC_CHECK_HEADERS([dmalloc.h],, [unset HAVE_DMALLOC])
if test "x$HAVE_DMALLOC" = "xyes"; then
AC_CHECK_LIB([dmalloc], [dmalloc_shutdown],, [unset HAVE_DMALLOC])
fi
2002-07-13 02:29:41 +08:00
if test -z "$HAVE_DMALLOC" -a -n "$HDF5_CONFIG_ABORT"; then
2012-09-12 04:11:44 +08:00
AC_MSG_ERROR([couldn't find dmalloc library])
2002-07-13 02:29:41 +08:00
fi
;;
no)
HAVE_DMALLOC="no"
2012-09-12 04:11:44 +08:00
AC_MSG_CHECKING([for dmalloc library])
AC_MSG_RESULT([suppressed])
2002-07-13 02:29:41 +08:00
;;
*)
HAVE_DMALLOC="yes"
case "$withval" in
*,*)
dmalloc_inc="`echo $withval |cut -f1 -d,`"
dmalloc_lib="`echo $withval |cut -f2 -d, -s`"
;;
*)
if test -n "$withval"; then
dmalloc_inc="$withval/include"
dmalloc_lib="$withval/lib"
fi
;;
esac
saved_CPPFLAGS="$CPPFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_CPPFLAGS="$AM_CPPFLAGS"
2002-07-13 02:29:41 +08:00
saved_LDFLAGS="$LDFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_LDFLAGS="$AM_LDFLAGS"
2002-07-13 02:29:41 +08:00
if test -n "$dmalloc_inc"; then
CPPFLAGS="$CPPFLAGS -I$dmalloc_inc"
2009-10-15 05:43:05 +08:00
AM_CPPFLAGS="$AM_CPPFLAGS -I$dmalloc_inc"
2002-07-13 02:29:41 +08:00
fi
2013-03-14 06:34:23 +08:00
AC_CHECK_HEADERS([dmalloc.h],,[CPPFLAGS="$saved_CPPFLAGS"; AM_CPPFLAGS="$saved_AM_CPPFLAGS"] [unset HAVE_DMALLOC])
2002-07-13 02:29:41 +08:00
2013-03-14 06:34:23 +08:00
if test "x$HAVE_DMALLOC" = "xyes"; then
if test -n "$dmalloc_lib"; then
LDFLAGS="$LDFLAGS -L$dmalloc_lib"
AM_LDFLAGS="$AM_LDFLAGS -L$dmalloc_lib"
fi
2002-07-13 02:29:41 +08:00
2013-03-14 06:34:23 +08:00
AC_CHECK_LIB([dmalloc], [dmalloc_shutdown],, [LDFLAGS="$saved_LDFLAGS"; AM_LDFLAGS="$saved_AM_LDFLAGS"; unset HAVE_DMALLOC])
fi
[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
2002-07-13 02:29:41 +08:00
if test -z "$HAVE_DMALLOC" -a -n "$HDF5_CONFIG_ABORT"; then
2012-09-12 04:11:44 +08:00
AC_MSG_ERROR([couldn't find dmalloc library])
2002-07-13 02:29:41 +08:00
fi
;;
esac
2016-01-28 05:45:23 +08:00
## ----------------------------------------------------------------------
## Make the external filters list available to *.in files
## At this point it's unset (no external filters by default) but it
## will be filled in during the deflate (zlib) and szip processing
## below.
##
AC_SUBST([EXTERNAL_FILTERS])
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Is the GNU zlib present? It has a header file `zlib.h' and a library
## `-lz' and their locations might be specified with the `--with-zlib'
## command-line switch. The value is an include path and/or a library path.
## If the library path is specified then it must be preceded by a comma.
##
AC_SUBST([USE_FILTER_DEFLATE]) USE_FILTER_DEFLATE="no"
2002-07-18 00:10:46 +08:00
AC_ARG_WITH([zlib],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--with-zlib=DIR],
2003-04-05 01:54:25 +08:00
[Use zlib library for external deflate I/O
filter [default=yes]])],,
2012-09-12 04:11:44 +08:00
[withval=yes])
2001-01-04 14:34:06 +08:00
case $withval in
2001-07-31 06:48:40 +08:00
yes)
2001-09-19 03:26:46 +08:00
HAVE_ZLIB="yes"
2013-03-14 06:34:23 +08:00
AC_CHECK_HEADERS([zlib.h], [HAVE_ZLIB_H="yes"], [unset HAVE_ZLIB])
if test "x$HAVE_ZLIB" = "xyes" -a "x$HAVE_ZLIB_H" = "xyes"; then
AC_CHECK_LIB([z], [compress2],, [unset HAVE_ZLIB])
fi
if test -z "$HAVE_ZLIB"; then
if test -n "$HDF5_CONFIG_ABORT"; then
AC_MSG_ERROR([couldn't find zlib library])
fi
else
AC_CHECK_FUNC([compress2], [HAVE_COMPRESS2="yes"])
2002-04-23 07:44:41 +08:00
fi
2001-07-31 06:48:40 +08:00
;;
no)
2001-09-19 03:26:46 +08:00
HAVE_ZLIB="no"
2015-03-31 02:55:21 +08:00
AC_MSG_CHECKING([for zlib])
2002-07-18 00:10:46 +08:00
AC_MSG_RESULT([suppressed])
2001-07-31 06:48:40 +08:00
;;
*)
2001-09-19 03:26:46 +08:00
HAVE_ZLIB="yes"
2001-08-11 05:34:40 +08:00
case "$withval" in
*,*)
2013-03-14 06:34:23 +08:00
zlib_inc="`echo $withval | cut -f1 -d,`"
zlib_lib="`echo $withval | cut -f2 -d, -s`"
2001-08-11 05:34:40 +08:00
;;
*)
if test -n "$withval"; then
zlib_inc="$withval/include"
zlib_lib="$withval/lib"
fi
;;
esac
saved_CPPFLAGS="$CPPFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_CPPFLAGS="$AM_CPPFLAGS"
2001-08-11 05:34:40 +08:00
saved_LDFLAGS="$LDFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_LDFLAGS="$AM_LDFLAGS"
2001-08-11 05:34:40 +08:00
2001-07-31 06:48:40 +08:00
if test -n "$zlib_inc"; then
CPPFLAGS="$CPPFLAGS -I$zlib_inc"
2009-10-15 05:43:05 +08:00
AM_CPPFLAGS="$AM_CPPFLAGS -I$zlib_inc"
2001-07-31 06:48:40 +08:00
fi
2002-07-18 00:10:46 +08:00
AC_CHECK_HEADERS([zlib.h],
2009-10-15 05:43:05 +08:00
[HAVE_ZLIB_H="yes"],
2013-03-14 06:34:23 +08:00
[CPPFLAGS="$saved_CPPFLAGS"; AM_CPPFLAGS="$saved_AM_CPPFLAGS"] [unset HAVE_ZLIB])
2001-07-31 06:48:40 +08:00
if test -n "$zlib_lib"; then
LDFLAGS="$LDFLAGS -L$zlib_lib"
2009-10-15 05:43:05 +08:00
AM_LDFLAGS="$AM_LDFLAGS -L$zlib_lib"
2001-07-31 06:48:40 +08:00
fi
2001-08-11 05:34:40 +08:00
2013-03-14 06:34:23 +08:00
if test "x$HAVE_ZLIB" = "xyes" -a "x$HAVE_ZLIB_H" = "xyes"; then
AC_CHECK_LIB([z], [compress2],,
[LDFLAGS="$saved_LDFLAGS"; AM_LDFLAGS="$saved_AM_LDFLAGS"; unset HAVE_ZLIB])
fi
2002-04-23 07:44:41 +08:00
2013-03-14 06:34:23 +08:00
if test -z "$HAVE_ZLIB"; then
if test -n "$HDF5_CONFIG_ABORT"; then
AC_MSG_ERROR([couldn't find zlib library])
fi
else
AC_CHECK_FUNC([compress2], [HAVE_COMPRESS2="yes"])
2002-04-23 07:44:41 +08:00
fi
2001-07-31 06:48:40 +08:00
;;
2001-01-04 14:34:06 +08:00
esac
1998-11-13 23:06:06 +08:00
2002-07-18 00:10:46 +08:00
if test "x$HAVE_ZLIB" = "xyes" -a "x$HAVE_ZLIB_H" = "xyes" -a "x$HAVE_COMPRESS2" = "xyes"; then
2013-03-14 06:34:23 +08:00
AC_DEFINE([HAVE_FILTER_DEFLATE], [1], [Define if support for deflate (zlib) filter is enabled])
USE_FILTER_DEFLATE="yes"
2003-04-05 01:54:25 +08:00
2013-03-14 06:34:23 +08:00
## Add "deflate" to external filter list
if test "X$EXTERNAL_FILTERS" != "X"; then
EXTERNAL_FILTERS="${EXTERNAL_FILTERS},"
fi
2016-01-28 05:45:23 +08:00
EXTERNAL_FILTERS="${EXTERNAL_FILTERS}deflate(zlib)"
2003-04-05 01:54:25 +08:00
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Is the szlib present? It has a header file `szlib.h' and a library
## `-lsz' and their locations might be specified with the `--with-szlib'
## command-line switch. The value is an include path and/or a library path.
## If the library path is specified then it must be preceded by a comma.
##
AC_SUBST([USE_FILTER_SZIP]) USE_FILTER_SZIP="no"
2003-04-05 01:54:25 +08:00
AC_ARG_WITH([szlib],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--with-szlib=DIR],
2003-04-05 01:54:25 +08:00
[Use szlib library for external szlib I/O
2003-05-16 07:25:38 +08:00
filter [default=no]])],,
2012-09-12 04:11:44 +08:00
[withval=no])
2003-04-05 01:54:25 +08:00
case $withval in
yes)
HAVE_SZLIB="yes"
2013-03-14 06:34:23 +08:00
AC_CHECK_HEADERS([szlib.h], [HAVE_SZLIB_H="yes"], [unset HAVE_SZLIB])
if test "x$HAVE_SZLIB" = "xyes" -a "x$HAVE_SZLIB_H" = "xyes"; then
AC_CHECK_LIB([sz], [SZ_BufftoBuffCompress],, [unset HAVE_SZLIB])
fi
2003-04-05 01:54:25 +08:00
if test -z "$HAVE_SZLIB" -a -n "$HDF5_CONFIG_ABORT"; then
AC_MSG_ERROR([couldn't find szlib library])
fi
;;
no)
HAVE_SZLIB="no"
AC_MSG_CHECKING([for szlib])
AC_MSG_RESULT([suppressed])
;;
*)
HAVE_SZLIB="yes"
case "$withval" in
*,*)
szlib_inc="`echo $withval |cut -f1 -d,`"
szlib_lib="`echo $withval |cut -f2 -d, -s`"
;;
*)
if test -n "$withval"; then
szlib_inc="$withval/include"
szlib_lib="$withval/lib"
fi
;;
esac
2015-06-17 05:25:03 +08:00
2003-04-05 01:54:25 +08:00
saved_CPPFLAGS="$CPPFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_CPPFLAGS="$AM_CPPFLAGS"
2003-04-05 01:54:25 +08:00
saved_LDFLAGS="$LDFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_LDFLAGS="$AM_LDFLAGS"
2015-06-17 05:25:03 +08:00
2003-04-05 01:54:25 +08:00
if test -n "$szlib_inc"; then
CPPFLAGS="$CPPFLAGS -I$szlib_inc"
2009-10-15 05:43:05 +08:00
AM_CPPFLAGS="$AM_CPPFLAGS -I$szlib_inc"
2003-04-05 01:54:25 +08:00
fi
2015-06-17 05:25:03 +08:00
2003-04-05 01:54:25 +08:00
AC_CHECK_HEADERS([szlib.h],
2009-10-15 05:43:05 +08:00
[HAVE_SZLIB_H="yes"],
2013-04-04 04:47:37 +08:00
[CPPFLAGS="$saved_CPPFLAGS"; AM_CPPFLAGS="$saved_AM_CPPFLAGS"] [unset HAVE_SZLIB])
[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
2003-04-05 01:54:25 +08:00
if test -n "$szlib_lib"; then
LDFLAGS="$LDFLAGS -L$szlib_lib"
2009-10-15 05:43:05 +08:00
AM_LDFLAGS="$AM_LDFLAGS -L$szlib_lib"
2003-04-05 01:54:25 +08:00
fi
2015-06-17 05:25:03 +08:00
2013-03-14 06:34:23 +08:00
if test "x$HAVE_SZLIB" = "xyes" -a "x$HAVE_SZLIB_H" = "xyes"; then
AC_CHECK_LIB([sz], [SZ_BufftoBuffCompress],,
[LDFLAGS="$saved_LDFLAGS"; AM_LDFLAGS="$saved_AM_LDFLAGS"; unset HAVE_SZLIB])
fi
[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
2003-04-05 01:54:25 +08:00
if test -z "$HAVE_SZLIB" -a -n "$HDF5_CONFIG_ABORT"; then
AC_MSG_ERROR([couldn't find szlib library])
fi
;;
esac
if test "x$HAVE_SZLIB" = "xyes" -a "x$HAVE_SZLIB_H" = "xyes"; then
2013-03-14 06:34:23 +08:00
## SZLIB library is available. Check if it can encode
AC_MSG_CHECKING([for szlib encoder])
2008-10-25 01:19:34 +08:00
2013-03-14 06:34:23 +08:00
## Set LD_LIBRARY_PATH so encoder test can find the library and run.
2015-06-17 05:25:03 +08:00
## Also add LL_PATH substitution to Makefiles so they can use the
2013-03-14 06:34:23 +08:00
## path as well, for testing examples.
if test -z "$LD_LIBRARY_PATH"; then
2008-10-25 01:19:34 +08:00
export LD_LIBRARY_PATH="$szlib_lib"
2013-03-14 06:34:23 +08:00
else
2014-10-14 11:14:29 +08:00
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$szlib_lib"
2013-03-14 06:34:23 +08:00
fi
2008-10-25 05:30:07 +08:00
2013-03-14 06:34:23 +08:00
AC_SUBST([LL_PATH]) LL_PATH="$LD_LIBRARY_PATH"
2012-09-18 00:10:12 +08:00
2013-03-14 06:34:23 +08:00
AC_CACHE_VAL([hdf5_cv_szlib_can_encode],
2015-03-30 22:45:22 +08:00
[AC_RUN_IFELSE(
[AC_LANG_PROGRAM([
#include "szlib.h"
],[[
2004-07-02 01:38:04 +08:00
/* SZ_encoder_enabled returns 1 if encoder is present */
2015-03-30 22:45:22 +08:00
if(SZ_encoder_enabled() == 1)
exit(0);
else
exit(1);
]])]
, [hdf5_cv_szlib_can_encode=yes], [hdf5_cv_szlib_can_encode=no],)]
)
2015-06-17 05:25:03 +08:00
AC_DEFINE([HAVE_FILTER_SZIP], [1],
2008-10-25 01:19:34 +08:00
[Define if support for szip filter is enabled])
2013-03-14 06:34:23 +08:00
USE_FILTER_SZIP="yes"
2012-09-18 00:10:12 +08:00
2013-03-14 06:34:23 +08:00
if test ${hdf5_cv_szlib_can_encode} = "yes"; then
AC_MSG_RESULT([yes])
2015-06-17 05:25:03 +08:00
fi
2013-03-14 06:34:23 +08:00
if test ${hdf5_cv_szlib_can_encode} = "no"; then
AC_MSG_RESULT([no])
2015-06-17 05:25:03 +08:00
fi
2013-03-14 06:34:23 +08:00
## Add "szip" to external filter list
if test ${hdf5_cv_szlib_can_encode} = "yes"; then
if test "X$EXTERNAL_FILTERS" != "X"; then
EXTERNAL_FILTERS="${EXTERNAL_FILTERS},"
[svn-r9493] Purpose:
Fix SZIP filter to dynmically detect encoder.
Description:
Solution:
See:
http://hdf.ncsa.uiuc.edu/RFC/SZIP/Szip_dynamic_12_Oct.pdf
Platforms tested:
verbena, arabica, cobalt.
Note RE testing:
All automatic tests work as before.
The feature is a configuration thing, so the tests are manual.
Tested with the following configs:
pre-release version of SZIP, with dynamic library,
1. no SZIP
2. SZIP, decoder only
3. SZIP, encoder+decoder
released (static lib) SZIP
4. no SZIP
5. SZIP, decoder only
6. SZIP, encoder+decoder
after build, switch szip in LD_LIBRARY_PATH at run time
7. SZIP decoder
8. SZIP encoder
Misc. update:
Manifest updated
2004-11-03 03:10:24 +08:00
fi
2016-01-28 05:45:23 +08:00
EXTERNAL_FILTERS="${EXTERNAL_FILTERS}szip(encoder)"
2015-06-17 05:25:03 +08:00
fi
2013-03-14 06:34:23 +08:00
if test ${hdf5_cv_szlib_can_encode} = "no"; then
if test "X$EXTERNAL_FILTERS" != "X"; then
EXTERNAL_FILTERS="${EXTERNAL_FILTERS},"
fi
2016-01-28 05:45:23 +08:00
EXTERNAL_FILTERS="${EXTERNAL_FILTERS}szip(no encoder)"
2013-03-14 06:34:23 +08:00
fi
[svn-r6549] Purpose:
This is the first check-in message related to szip support at HDF5 1.6 release
Description:
szip compression support is required by NASA ESDIS. The compression algorithm
is a good compression algorithm for scientific data. In HDF5, we add another filter
function to make szip as a default compression package as we did for gzip(or zlib).
Solution:
In the configure.in and configure, I handled szip exactly the same as what zlib was built into
the HDF5.
Currently if you don't specify in the configure command line with:
./configure --with-szlib=/.....
Unless you put your szip library in your path,you will build the same HDF5 library like before.
Also, I only use static szip library to test with HDF5.
Platforms tested:
Since there are changes of configure.in and configure,I didn't use h5committest.
I tested with four platforms.
1) Linux 2.4 (eirene)
2) Solaris 2.7(arabica)
3) windows 2000(VS 6.0)
4) SGI IRIX6.5-64(modi4)
For test 1)-3), only basic C tests were done
For modi4 test, I tested 64-bit C,parallel and fortran.
ALl tests passed, except a warning message from szip library when checksum is used in some order, which doesn't cause any real problems.
Misc. update:
2003-04-01 23:18:40 +08:00
fi
2011-04-27 02:41:01 +08:00
AM_CONDITIONAL([BUILD_SHARED_SZIP_CONDITIONAL], [test "X$USE_FILTER_SZIP" = "Xyes" && test "X$LL_PATH" != "X"])
2008-10-25 01:19:34 +08:00
2012-09-12 04:11:44 +08:00
## Checkpoint the cache
2000-04-21 02:41:51 +08:00
AC_CACHE_SAVE
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2014-03-21 23:19:07 +08:00
## Enable thread-safe version of library. It requires Pthreads support
## on POSIX systems.
2012-09-12 04:11:44 +08:00
##
2016-01-28 05:45:23 +08:00
AC_SUBST([THREADSAFE])
## Default is no thread-safety
THREADSAFE=no
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for thread safe support])
2002-07-18 00:10:46 +08:00
AC_ARG_ENABLE([threadsafe],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-threadsafe],
2015-09-08 07:44:41 +08:00
[Enable thread-safe capability. Not compatible with the high-level library, Fortran, or C++ wrappers.
2015-03-10 11:35:13 +08:00
[default=no]])],
2012-09-12 04:11:44 +08:00
[THREADSAFE=$enableval])
2000-09-15 06:19:24 +08:00
2016-03-22 15:59:28 +08:00
## The high-level, C++, Fortran and Java interfaces are not compatible
2015-03-10 11:35:13 +08:00
## with the thread-safety option because the lock is not hoisted
## into the higher-level API calls.
2015-09-08 07:44:41 +08:00
## --enable-threadsafe is incompatible with --enable-hl unless
## --enable-unsupported has been specified on the configure line.
##
## Note that the high-level library is enabled by default so most
## users will have to add --disable-hl to the configure options.
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${HDF5_HL}" = "Xyes" -a "X${enable_threadsafe}" = "Xyes"; then
AC_MSG_ERROR([The thread-safe library is incompatible with the high-level library. --disable-hl can be used to prevent building the high-level library (recommended). Alternatively, --enable-unsupported will allow building the high-level library, though this configuration is not supported by The HDF Group.])
fi
fi
2012-09-18 00:10:12 +08:00
## The --enable-threadsafe flag is not compatible with --enable-cxx.
## If the user tried to specify both flags, throw an error, unless
## they also provided the --enable-unsupported flag.
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${HDF_CXX}" = "Xyes" -a "X${enable_threadsafe}" = "Xyes"; then
AC_MSG_ERROR([--enable-cxx and --enable-threadsafe flags are incompatible. Use --enable-unsupported to override this error.])
fi
fi
2015-03-10 11:35:13 +08:00
## --enable-threadsafe is also incompatible with --enable-fortran unless
2012-09-18 00:10:12 +08:00
## --enable-unsupported has been specified on the configure line.
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${HDF_FORTRAN}" = "Xyes" -a "X${enable_threadsafe}" = "Xyes"; then
AC_MSG_ERROR([--enable-fortran and --enable-threadsafe flags are incompatible. Use --enable-unsupported to override this error.])
fi
fi
2016-03-22 15:59:28 +08:00
## --enable-threadsafe is also incompatible with --enable-java unless
## --enable-unsupported has been specified on the configure line.
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${HDF_JAVA}" = "Xyes" -a "X${enable_threadsafe}" = "Xyes"; then
AC_MSG_ERROR([--enable-java and --enable-threadsafe flags are incompatible. Use --enable-unsupported to override this error.])
fi
fi
2015-03-10 11:35:13 +08:00
2000-09-15 06:19:24 +08:00
case "X-$THREADSAFE" in
2001-09-18 06:47:02 +08:00
X-|X-no)
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([no])
2001-09-18 06:47:02 +08:00
;;
X-yes)
2015-06-17 05:25:03 +08:00
THREADSAFE=yes
2014-03-21 23:19:07 +08:00
AC_MSG_RESULT([yes])
2001-09-18 06:47:02 +08:00
;;
*)
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([error])
AC_MSG_ERROR([\'$enableval\' is not a valid threadsafe type])
2001-09-18 06:47:02 +08:00
;;
2000-04-11 02:23:38 +08:00
esac
2000-06-06 07:25:29 +08:00
2000-09-15 06:19:24 +08:00
if test "X$THREADSAFE" = "Xyes"; then
2014-03-21 23:19:07 +08:00
AC_DEFINE([HAVE_THREADSAFE], [1], [Define if we have thread safe support])
## ----------------------------------------------------------------------
2015-03-10 11:35:13 +08:00
## Is the Pthreads library present? It has a header file `pthread.h' and
2014-03-21 23:19:07 +08:00
## a library `-lpthread' and their locations might be specified with the
## `--with-pthread' command-line switch. The value is an include path
## and/or a library path. If the library path is specified then it must
## be preceded by a comma.
##
## Thread-safety in HDF5 only uses Pthreads via configure, so the
2015-03-10 11:35:13 +08:00
## default is "check", though this only has an effect when
2014-03-21 23:19:07 +08:00
## --enable-threadsafe is specified.
AC_SUBST([HAVE_PTHREAD]) HAVE_PTHREAD=yes
AC_ARG_WITH([pthread],
[AS_HELP_STRING([--with-pthread=DIR],
2015-03-10 11:35:13 +08:00
[Specify alternative path to Pthreads library when
thread-safe capability is built.])],,
[withval=check])
2014-03-21 23:19:07 +08:00
case "$withval" in
2015-03-10 11:35:13 +08:00
check | yes)
2014-03-21 23:19:07 +08:00
AC_CHECK_HEADERS([pthread.h],, [unset HAVE_PTHREAD])
if test "x$HAVE_PTHREAD" = "xyes"; then
AC_CHECK_LIB([pthread], [pthread_self],, [unset HAVE_PTHREAD])
fi
;;
no)
2015-03-10 11:35:13 +08:00
AC_MSG_ERROR([Must use Pthreads with thread safety])
2014-03-21 23:19:07 +08:00
;;
*)
case "$withval" in
*,*)
pthread_inc="`echo $withval | cut -f1 -d,`"
pthread_lib="`echo $withval | cut -f2 -d, -s`"
;;
*)
if test -n "$withval"; then
pthread_inc="$withval/include"
pthread_lib="$withval/lib"
fi
;;
esac
if test -n "$pthread_inc"; then
saved_CPPFLAGS="$CPPFLAGS"
saved_AM_CPPFLAGS="$AM_CPPFLAGS"
CPPFLAGS="$CPPFLAGS -I$pthread_inc"
AM_CPPFLAGS="$AM_CPPFLAGS -I$pthread_inc"
AC_CHECK_HEADERS([pthread.h],, [CPPFLAGS="$saved_CPPFLAGS"; AM_CPPFLAGS="$saved_AM_CPPFLAGS"; unset HAVE_PTHREAD])
else
AC_CHECK_HEADERS([pthread.h],, [unset HAVE_PTHREAD])
fi
if test "x$HAVE_PTHREAD" = "xyes"; then
if test -n "$pthread_lib"; then
saved_LDFLAGS="$LDFLAGS"
saved_AM_LDFLAGS="$AM_LDFLAGS"
LDFLAGS="$LDFLAGS -L$pthread_lib"
AM_LDFLAGS="$AM_LDFLAGS -L$pthread_lib"
AC_CHECK_LIB([pthread], [pthread_self],,
[LDFLAGS="$saved_LDFLAGS"; AM_LDFLAGS="$saved_AM_LDFLAGS"; unset HAVE_PTHREAD])
else
AC_CHECK_LIB([pthread], [pthread_self],, [unset HAVE_PTHREAD])
fi
fi
;;
esac
2015-03-10 11:35:13 +08:00
## ----------------------------------------------------------------------
## Check if pthread_attr_setscope(&attribute, PTHREAD_SCOPE_SYSTEM)
## is supported on this system
##
## Unfortunately, this probably needs to be an AC_RUN_IFELSE since
## it's impossible to determine if PTHREAD_SCOPE_SYSTEM is
## supported a priori. POSIX.1-2001 requires that a conformant
## system need only support one of SYSTEM or PROCESS scopes.
##
## For cross-compiling, we've added a pessimistic 'no'. You can
## hand-hack the config file if you know otherwise.
AC_MSG_CHECKING([Pthreads supports system scope])
AC_CACHE_VAL([hdf5_cv_system_scope_threads],
[AC_RUN_IFELSE(
[AC_LANG_PROGRAM([
#if STDC_HEADERS
#include <stdlib.h>
#include <pthread.h>
#endif
],[
pthread_attr_t attribute;
int ret;
pthread_attr_init(&attribute);
ret=pthread_attr_setscope(&attribute, PTHREAD_SCOPE_SYSTEM);
exit(ret==0 ? 0 : 1);
])]
, [hdf5_cv_system_scope_threads=yes], [hdf5_cv_system_scope_threads=no], [hdf5_cv_system_scope_threads=no])])
if test ${hdf5_cv_system_scope_threads} = "yes"; then
AC_DEFINE([SYSTEM_SCOPE_THREADS], [1],
[Define if your system supports pthread_attr_setscope(&attribute, PTHREAD_SCOPE_SYSTEM) call.])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
AC_MSG_NOTICE([Always 'no' if cross-compiling. Edit the config file if your platform supports pthread_attr_setscope(&attribute, PTHREAD_SCOPE_SYSTEM).])
fi
2000-04-11 02:23:38 +08:00
fi
1999-12-21 04:23:33 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check for MONOTONIC_TIMER support (used in clock_gettime). This has
2015-09-09 04:03:41 +08:00
## to be done after any POSIX defines to ensure that the test gets
2012-09-12 04:11:44 +08:00
## the correct POSIX level on linux.
AC_CHECK_DECL([CLOCK_MONOTONIC],[have_clock_monotonic="yes"],[have_clock_monotonic="no"],[[#include <time.h>]])
2011-10-12 03:04:46 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## How does one figure out the local time zone? Anyone know of a
## Posix way to do this?
##
1998-07-30 00:43:59 +08:00
2012-09-12 04:11:44 +08:00
## First check if `struct tm' has a `tm_gmtoff' member.
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for tm_gmtoff in struct tm])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
2012-09-12 04:11:44 +08:00
#include <sys/time.h>
2015-09-19 20:24:40 +08:00
#include <time.h>
]], [[struct tm tm; tm.tm_gmtoff=0;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_TM_GMTOFF], [1],
2015-09-19 20:24:40 +08:00
[Define if tm_gmtoff is a member of struct tm])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
1998-07-30 00:43:59 +08:00
2012-09-12 04:11:44 +08:00
## Check whether the global variable `timezone' is defined.
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for global timezone variable])
2008-05-01 03:51:13 +08:00
case "`uname`" in
CYGWIN*)
AC_MSG_RESULT([disabled in CYGWIN])
;;
*)
2015-09-19 20:24:40 +08:00
AC_LINK_IFELSE([AC_LANG_PROGRAM([[
2008-05-01 03:51:13 +08:00
#include <sys/time.h>
2015-09-19 20:24:40 +08:00
#include <time.h>]], [[timezone=0;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_TIMEZONE], [1],
2015-09-19 20:24:40 +08:00
[Define if timezone is a global variable])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
2008-05-01 03:51:13 +08:00
;;
esac
1998-07-30 00:43:59 +08:00
2004-07-24 01:29:16 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Does the struct stat have the st_blocks field? This field is not Posix.
##
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for st_blocks in struct stat])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM[[
#include <sys/stat.h>]],[[struct stat sb; sb.st_blocks=0;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_STAT_ST_BLOCKS], [1],
2015-09-19 20:24:40 +08:00
[Define if struct stat has the st_blocks field])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
[svn-r339] Changes since 19980408
----------------------
./src/H5Osdspace.c
./html/H5.format.html
In the past we were allowed to have >2GB files on a 32-bit
machine as long as no dataset within the file was larger than
4GB (or whatever sizeof(size_t) is). That's been fixed now.
All dataset size calculations are done with `hsize_t' which is
normally defined as `unsigned long long'.
./src/H5F.c
./src/H5Ffamily.c
./src/H5Fprivate.h
./src/H5P.c
./src/H5Ppublic.h
The file family member size can now be set/queried. The
default is still 64MB, but it can be set to 1GB by saying:
H5Pset_family (plist, 30, H5P_DEFAULT);
When opening an existing file family the specified
bits-per-member is ignored and the first member of the family
determines the bits-per-member, which can be retrieved with
H5Pget_family().
./acconfig.h
./configure.in
./src/H5config.h
./src/H5public.h
Added `--disable-hsizet' so that those with old GCC compilers
(<2.8.1) can still compile the code.
./src/H5.c
./src/H5private.h
Added HDfprintf() which works just like fprintf() except you
can give `H' as a size modifier for the integer conversions
and supply an `hsize_t' or `hssize_t' argument without casting
it. For instance:
hsize_t npoints = H5Sget_npoints(space);
HDfprintf(stdout,"Dataset has %Hd (%#018Hx) points\n",
npoints, npoints);
You can now give `%a' as a format to print an address, but all
formating flags are ignored and it causes the return value of
HDfprintf() to not include the characters in the address (but
who uses the return value anyway :-). Example:
H5G_t *grp;
HDfprintf(stdout, "Group object header at %a\n",
&(grp->ent.header));
Added HDstrtoll() which works exactly like [HD]strtol() except
the result is an int64.
./src/debug.c
Large addresses can now be entered from the command-line. Use
either decimal, octal (leading `0') or hexadecimal (leading
`0x') when giving the address.
./src/h5ls.c
The printf format for dataset dimensions was changed to `%Hu'
to support large datasets.
./test/big.c [NEW]
A test for big datasets on 32-bit machines. This test is not
run by default. Don't try to run it on an nfs-mounted file
system or other file system that doesn't support holes because
it creates two 32GB datasets of all zero.
1998-04-10 04:22:11 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## How do we figure out the width of a tty in characters?
##
2013-08-14 01:53:23 +08:00
AC_CHECK_FUNCS([_getvideoconfig gettextinfo])
case "`uname`" in
CYGWIN*)
;;
*)
2016-08-02 02:22:17 +08:00
AC_CHECK_FUNCS([GetConsoleScreenBufferInfo getpwuid])
2013-08-14 01:53:23 +08:00
;;
esac
2012-09-12 04:11:44 +08:00
AC_CHECK_FUNCS([_scrsize ioctl])
[svn-r879] Changes since 19981105
----------------------
./configure.in
./acconfig.h
./configure [REGENERATED]
./src/H5config.h.in [REGENERATED]
Added checks for functions, structs, constants, and header
files used in h5ls.c to determine the output width with
various Windows compilers and Unix variants.
Added check for <sys/stat.h> and defined
HAVE_SYS_STAT_H. Included <sys/stat.h> in H5private.h outside
the Posix.1 #include's section.
./src/H5RA.c
Less aggressive about failing -- rather returns false, which
allows type detection to continue.
./src/h5ls.c
Data types are displayed for datasets and named data types when
`-v' or `--verbose' is specified on the command-line. The
algorithm is a little different than the dumper because we're
trying to be human-friendly, not necessarily machine-friendly.
* Any data type which matches a native C type gets printed
something like `native double'.
* A floating point type that matches one of the IEEE standard
types but not one of the native types gets printed like `IEEE
64-bit big-endian float'.
* Other floating point values have information about sign bit
location; exponent size, location, and bias; and significand
size, location, and normalization.
* Padding and offsets are displayed for types that have
padding (precision != size), including internal padding for
some floating point data types.
* Non-native integer types are displayed like `32-bit
little-endian unsigned integer'.
* Compound data types have each member displayed including the
member name, byte offset within the struct, dimensions, index
permutation, and data type.
* String types are displayed like `256-byte null-terminated
ASCII string'.
* References are displayed like `8-byte unknown reference'
until the reference interface stabilizes a little.
* All other types including types not yet defined will be
printed like `4-byte class-9 unknown'.
The dimensionality of scalar datasets is printed like `{SCALAR}'
instead of just `{}'.
If external raw files are used to store a dataset then the offsets,
sizes, and file names of each are printed if `-v' or `--verbose'
was given on the command-line.
If an object is found and h5ls can't determine the object type then
it still tries to print the number of hard links, the OID, and any
comment that might be present if `-v' or `--verbose' was specified.
If the `-d' or `--dump' switch is turned on then ragged arrays will
report that the data can only be dumped by dumping the component
datasets explicitly. I'm not planning to implement this since
we're going to eventually change the whole way ragged arrays are
stored.
Compound data values do not have the component names displayed by
default when `-v' or `--verbose' is turned on. Instead, the names
can be displayed with `-l' or `--label'.
The output width is determined by the first rule that applies:
* If the `-wN', `-w N' or `--width=N' switch appeared on
the command line then use N for the output width.
* Query the OS for the tty width in a highly unportable way
borrowed from GNU `less' depending on what functions and
data structures were found during configuration (if any):
_getvideoconfig(), gettextinfo(), _srcsize(), ioctl(),
GetConsoleScreenBufferInfo(), struct videoconfig, struct
text_info, the TIOCGWINSZ ioctl, the TIOCGETD ioctl.
* If the `COLUMNS' environment variable is set then use
its value.
* Use the value 80.
Just for kicks, run Mark and Jim's test_vbt and then say `h5ls -dlsv
test.vbt'. You can also try it on the various *.h5 files in the
test/example directories.
./config/linux
Removed turning on parallel by default on Robb's macine.
1998-11-07 02:00:22 +08:00
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for struct videoconfig])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]],[[struct videoconfig w; w.numtextcols=0;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_STRUCT_VIDEOCONFIG], [1],
2015-09-19 20:24:40 +08:00
[Define if struct videoconfig is defined])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
[svn-r879] Changes since 19981105
----------------------
./configure.in
./acconfig.h
./configure [REGENERATED]
./src/H5config.h.in [REGENERATED]
Added checks for functions, structs, constants, and header
files used in h5ls.c to determine the output width with
various Windows compilers and Unix variants.
Added check for <sys/stat.h> and defined
HAVE_SYS_STAT_H. Included <sys/stat.h> in H5private.h outside
the Posix.1 #include's section.
./src/H5RA.c
Less aggressive about failing -- rather returns false, which
allows type detection to continue.
./src/h5ls.c
Data types are displayed for datasets and named data types when
`-v' or `--verbose' is specified on the command-line. The
algorithm is a little different than the dumper because we're
trying to be human-friendly, not necessarily machine-friendly.
* Any data type which matches a native C type gets printed
something like `native double'.
* A floating point type that matches one of the IEEE standard
types but not one of the native types gets printed like `IEEE
64-bit big-endian float'.
* Other floating point values have information about sign bit
location; exponent size, location, and bias; and significand
size, location, and normalization.
* Padding and offsets are displayed for types that have
padding (precision != size), including internal padding for
some floating point data types.
* Non-native integer types are displayed like `32-bit
little-endian unsigned integer'.
* Compound data types have each member displayed including the
member name, byte offset within the struct, dimensions, index
permutation, and data type.
* String types are displayed like `256-byte null-terminated
ASCII string'.
* References are displayed like `8-byte unknown reference'
until the reference interface stabilizes a little.
* All other types including types not yet defined will be
printed like `4-byte class-9 unknown'.
The dimensionality of scalar datasets is printed like `{SCALAR}'
instead of just `{}'.
If external raw files are used to store a dataset then the offsets,
sizes, and file names of each are printed if `-v' or `--verbose'
was given on the command-line.
If an object is found and h5ls can't determine the object type then
it still tries to print the number of hard links, the OID, and any
comment that might be present if `-v' or `--verbose' was specified.
If the `-d' or `--dump' switch is turned on then ragged arrays will
report that the data can only be dumped by dumping the component
datasets explicitly. I'm not planning to implement this since
we're going to eventually change the whole way ragged arrays are
stored.
Compound data values do not have the component names displayed by
default when `-v' or `--verbose' is turned on. Instead, the names
can be displayed with `-l' or `--label'.
The output width is determined by the first rule that applies:
* If the `-wN', `-w N' or `--width=N' switch appeared on
the command line then use N for the output width.
* Query the OS for the tty width in a highly unportable way
borrowed from GNU `less' depending on what functions and
data structures were found during configuration (if any):
_getvideoconfig(), gettextinfo(), _srcsize(), ioctl(),
GetConsoleScreenBufferInfo(), struct videoconfig, struct
text_info, the TIOCGWINSZ ioctl, the TIOCGETD ioctl.
* If the `COLUMNS' environment variable is set then use
its value.
* Use the value 80.
Just for kicks, run Mark and Jim's test_vbt and then say `h5ls -dlsv
test.vbt'. You can also try it on the various *.h5 files in the
test/example directories.
./config/linux
Removed turning on parallel by default on Robb's macine.
1998-11-07 02:00:22 +08:00
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for struct text_info])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]], [[struct text_info w; w.screenwidth=0;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_STRUCT_TEXT_INFO], [1],
2015-09-19 20:24:40 +08:00
[Define if struct text_info is defined])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
[svn-r879] Changes since 19981105
----------------------
./configure.in
./acconfig.h
./configure [REGENERATED]
./src/H5config.h.in [REGENERATED]
Added checks for functions, structs, constants, and header
files used in h5ls.c to determine the output width with
various Windows compilers and Unix variants.
Added check for <sys/stat.h> and defined
HAVE_SYS_STAT_H. Included <sys/stat.h> in H5private.h outside
the Posix.1 #include's section.
./src/H5RA.c
Less aggressive about failing -- rather returns false, which
allows type detection to continue.
./src/h5ls.c
Data types are displayed for datasets and named data types when
`-v' or `--verbose' is specified on the command-line. The
algorithm is a little different than the dumper because we're
trying to be human-friendly, not necessarily machine-friendly.
* Any data type which matches a native C type gets printed
something like `native double'.
* A floating point type that matches one of the IEEE standard
types but not one of the native types gets printed like `IEEE
64-bit big-endian float'.
* Other floating point values have information about sign bit
location; exponent size, location, and bias; and significand
size, location, and normalization.
* Padding and offsets are displayed for types that have
padding (precision != size), including internal padding for
some floating point data types.
* Non-native integer types are displayed like `32-bit
little-endian unsigned integer'.
* Compound data types have each member displayed including the
member name, byte offset within the struct, dimensions, index
permutation, and data type.
* String types are displayed like `256-byte null-terminated
ASCII string'.
* References are displayed like `8-byte unknown reference'
until the reference interface stabilizes a little.
* All other types including types not yet defined will be
printed like `4-byte class-9 unknown'.
The dimensionality of scalar datasets is printed like `{SCALAR}'
instead of just `{}'.
If external raw files are used to store a dataset then the offsets,
sizes, and file names of each are printed if `-v' or `--verbose'
was given on the command-line.
If an object is found and h5ls can't determine the object type then
it still tries to print the number of hard links, the OID, and any
comment that might be present if `-v' or `--verbose' was specified.
If the `-d' or `--dump' switch is turned on then ragged arrays will
report that the data can only be dumped by dumping the component
datasets explicitly. I'm not planning to implement this since
we're going to eventually change the whole way ragged arrays are
stored.
Compound data values do not have the component names displayed by
default when `-v' or `--verbose' is turned on. Instead, the names
can be displayed with `-l' or `--label'.
The output width is determined by the first rule that applies:
* If the `-wN', `-w N' or `--width=N' switch appeared on
the command line then use N for the output width.
* Query the OS for the tty width in a highly unportable way
borrowed from GNU `less' depending on what functions and
data structures were found during configuration (if any):
_getvideoconfig(), gettextinfo(), _srcsize(), ioctl(),
GetConsoleScreenBufferInfo(), struct videoconfig, struct
text_info, the TIOCGWINSZ ioctl, the TIOCGETD ioctl.
* If the `COLUMNS' environment variable is set then use
its value.
* Use the value 80.
Just for kicks, run Mark and Jim's test_vbt and then say `h5ls -dlsv
test.vbt'. You can also try it on the various *.h5 files in the
test/example directories.
./config/linux
Removed turning on parallel by default on Robb's macine.
1998-11-07 02:00:22 +08:00
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for TIOCGWINSZ])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
#include <sys/ioctl.h>
]],[[int w=TIOCGWINSZ;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_TIOCGWINSZ], [1],
2002-04-03 06:08:23 +08:00
[Define if the ioctl TIOGWINSZ is defined])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
[svn-r879] Changes since 19981105
----------------------
./configure.in
./acconfig.h
./configure [REGENERATED]
./src/H5config.h.in [REGENERATED]
Added checks for functions, structs, constants, and header
files used in h5ls.c to determine the output width with
various Windows compilers and Unix variants.
Added check for <sys/stat.h> and defined
HAVE_SYS_STAT_H. Included <sys/stat.h> in H5private.h outside
the Posix.1 #include's section.
./src/H5RA.c
Less aggressive about failing -- rather returns false, which
allows type detection to continue.
./src/h5ls.c
Data types are displayed for datasets and named data types when
`-v' or `--verbose' is specified on the command-line. The
algorithm is a little different than the dumper because we're
trying to be human-friendly, not necessarily machine-friendly.
* Any data type which matches a native C type gets printed
something like `native double'.
* A floating point type that matches one of the IEEE standard
types but not one of the native types gets printed like `IEEE
64-bit big-endian float'.
* Other floating point values have information about sign bit
location; exponent size, location, and bias; and significand
size, location, and normalization.
* Padding and offsets are displayed for types that have
padding (precision != size), including internal padding for
some floating point data types.
* Non-native integer types are displayed like `32-bit
little-endian unsigned integer'.
* Compound data types have each member displayed including the
member name, byte offset within the struct, dimensions, index
permutation, and data type.
* String types are displayed like `256-byte null-terminated
ASCII string'.
* References are displayed like `8-byte unknown reference'
until the reference interface stabilizes a little.
* All other types including types not yet defined will be
printed like `4-byte class-9 unknown'.
The dimensionality of scalar datasets is printed like `{SCALAR}'
instead of just `{}'.
If external raw files are used to store a dataset then the offsets,
sizes, and file names of each are printed if `-v' or `--verbose'
was given on the command-line.
If an object is found and h5ls can't determine the object type then
it still tries to print the number of hard links, the OID, and any
comment that might be present if `-v' or `--verbose' was specified.
If the `-d' or `--dump' switch is turned on then ragged arrays will
report that the data can only be dumped by dumping the component
datasets explicitly. I'm not planning to implement this since
we're going to eventually change the whole way ragged arrays are
stored.
Compound data values do not have the component names displayed by
default when `-v' or `--verbose' is turned on. Instead, the names
can be displayed with `-l' or `--label'.
The output width is determined by the first rule that applies:
* If the `-wN', `-w N' or `--width=N' switch appeared on
the command line then use N for the output width.
* Query the OS for the tty width in a highly unportable way
borrowed from GNU `less' depending on what functions and
data structures were found during configuration (if any):
_getvideoconfig(), gettextinfo(), _srcsize(), ioctl(),
GetConsoleScreenBufferInfo(), struct videoconfig, struct
text_info, the TIOCGWINSZ ioctl, the TIOCGETD ioctl.
* If the `COLUMNS' environment variable is set then use
its value.
* Use the value 80.
Just for kicks, run Mark and Jim's test_vbt and then say `h5ls -dlsv
test.vbt'. You can also try it on the various *.h5 files in the
test/example directories.
./config/linux
Removed turning on parallel by default on Robb's macine.
1998-11-07 02:00:22 +08:00
2003-08-09 02:28:03 +08:00
AC_MSG_CHECKING([for TIOCGETD])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
#include <sys/ioctl.h>
]],[[int w=TIOCGETD;]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_TIOCGETD], [1],
2002-04-03 06:08:23 +08:00
[Define if the ioctl TIOCGETD is defined])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
## ----------------------------------------------------------------------
## Check for functions.
##
2015-02-23 14:56:16 +08:00
## NOTE: clock_gettime may require linking to the rt or posix4 library
## so we'll search for it before calling AC_CHECK_FUNCS.
AC_SEARCH_LIBS([clock_gettime], [rt posix4])
2015-12-11 16:19:10 +08:00
AC_CHECK_FUNCS([alarm clock_gettime difftime fcntl flock fork frexpf])
2016-08-02 02:22:17 +08:00
AC_CHECK_FUNCS([frexpl gethostname getrusage gettimeofday])
2015-02-23 14:56:16 +08:00
AC_CHECK_FUNCS([lstat rand_r random setsysinfo])
2012-09-12 04:11:44 +08:00
AC_CHECK_FUNCS([signal longjmp setjmp siglongjmp sigsetjmp sigprocmask])
AC_CHECK_FUNCS([snprintf srandom strdup symlink system])
2017-03-17 01:58:49 +08:00
AC_CHECK_FUNCS([strtoll strtoull])
2015-03-28 08:37:08 +08:00
AC_CHECK_FUNCS([tmpfile asprintf vasprintf vsnprintf waitpid])
2016-07-01 04:59:15 +08:00
AC_CHECK_FUNCS([roundf lroundf llroundf round lround llround])
1997-08-16 00:35:53 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check compiler characteristics
##
1997-10-21 07:14:35 +08:00
AC_C_CONST
2015-06-25 02:53:43 +08:00
AC_MSG_CHECKING([if the compiler understands __inline__])
AC_COMPILE_IFELSE(
[AC_LANG_SOURCE([[static __inline__ void f(void){return;};]])],
[AC_DEFINE([HAVE___INLINE__], [1], [Define if the compiler understands __inline__]) AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])]
)
AC_MSG_CHECKING([if the compiler understands __inline])
AC_COMPILE_IFELSE(
[AC_LANG_SOURCE([[static __inline void f(void){return;};]])],
[AC_DEFINE([HAVE___INLINE], [1], [Define if the compiler understands __inline]) AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])]
)
AC_MSG_CHECKING([if the compiler understands inline])
AC_COMPILE_IFELSE(
[AC_LANG_SOURCE([[static inline void f(void){return;};]])],
[AC_DEFINE([HAVE_INLINE], [1], [Define if the compiler understands inline]) AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])]
)
1997-10-21 07:14:35 +08:00
2002-07-18 00:10:46 +08:00
AC_MSG_CHECKING([for __attribute__ extension])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]],[[int __attribute__((unused)) x]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_ATTRIBUTE], [1],
2002-04-03 06:08:23 +08:00
[Define if the __attribute__(()) extension is present])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
1997-10-21 07:14:35 +08:00
2008-09-17 22:04:35 +08:00
AC_MSG_CHECKING([for __func__ extension])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]],[[ const char *fname = __func__; ]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_C99_FUNC], [1],
2009-01-14 21:09:42 +08:00
[Define if the compiler understands the __func__ keyword])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
2002-07-18 00:10:46 +08:00
AC_MSG_CHECKING([for __FUNCTION__ extension])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]],,[[ const char *fname = __FUNCTION__; ]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_FUNCTION], [1],
2009-01-14 21:09:42 +08:00
[Define if the compiler understands the __FUNCTION__ keyword])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
2009-01-14 21:09:42 +08:00
AC_MSG_CHECKING([for C99 designated initialization support])
2015-09-19 20:24:40 +08:00
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]], [[
2009-01-14 21:09:42 +08:00
typedef struct {
int x;
union {
int i;
double d;
} u;
} di_struct_t;
2016-03-01 22:50:49 +08:00
di_struct_t x = {0, { .d = 0.0}}; ]])],
2012-09-12 04:11:44 +08:00
[AC_DEFINE([HAVE_C99_DESIGNATED_INITIALIZER], [1],
2009-01-14 21:09:42 +08:00
[Define if the compiler understands C99 designated initialization of structs and unions])
2012-09-12 04:11:44 +08:00
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])])
## ----------------------------------------------------------------------
## Try to figure out how to print `long long'. Some machines use `%lld'
## and others use `%qd'. There may be more! The final `l' is a
## default in case none of the others work.
##
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([how to print long long])
2012-09-12 04:11:44 +08:00
AC_CACHE_VAL([hdf5_cv_printf_ll], [
2000-09-15 06:19:24 +08:00
2004-12-29 22:26:20 +08:00
for hdf5_cv_printf_ll in l ll L q unknown; do
2015-03-30 22:45:22 +08:00
AC_RUN_IFELSE(
[AC_LANG_PROGRAM([
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
],[[
char *s = malloc(128);
long long x = (long long)1048576 * (long long)1048576;
sprintf(s,"%${hdf5_cv_printf_ll}d",x);
exit(strcmp(s,"1099511627776"));
]])]
, [break],,[continue])
2012-09-12 04:11:44 +08:00
done])
2000-09-15 06:19:24 +08:00
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([%${hdf5_cv_printf_ll}d and %${hdf5_cv_printf_ll}u])
2015-06-17 05:25:03 +08:00
AC_DEFINE_UNQUOTED([PRINTF_LL_WIDTH], ["$hdf5_cv_printf_ll"],
2005-02-01 11:17:02 +08:00
[Width for printf() for type `long long' or `__int64', use `ll'])
1998-04-25 05:26:32 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
2017-06-29 07:49:58 +08:00
## Remove old ways of determining debug/production build.
## These were used in 1.8.x and earlier. We should probably keep these checks
## around to help people migrate to 1.10.x and newer versions.
2012-09-12 04:11:44 +08:00
##
2002-07-18 00:10:46 +08:00
AC_ARG_ENABLE([debug],
2017-06-29 07:49:58 +08:00
[AS_HELP_STRING([--enable-debug], [DEPRECATED: use --enable-build-mode=debug])],
[AC_MSG_ERROR([--enable-debug is deprecated, use --enable-build-mode=debug instead.])])
2016-01-28 05:45:23 +08:00
AC_ARG_ENABLE([production],
2017-06-29 07:49:58 +08:00
[AS_HELP_STRING([--enable-production], [DEPRECATED: use --enable-build-mode=production])],
[AC_MSG_ERROR([--enable-production is deprecated, use --enable-build-mode=production instead.])])
2016-01-28 05:45:23 +08:00
## ----------------------------------------------------------------------
## Check if the compiler should include symbols
##
AC_MSG_CHECKING([enable debugging symbols])
AC_ARG_ENABLE([symbols],
[AS_HELP_STRING([--enable-symbols=(yes|no|<custom>)],
[Add debug symbols to the library (e.g.: build with -g).
This is independent of the build mode and optimization
level. The custom string allows special settings like
-ggdb, etc. to be used.
[default=yes if debug build, otherwise no]
2007-05-01 11:38:52 +08:00
])],
2016-01-28 05:45:23 +08:00
[SYMBOLS=$enableval])
2002-07-18 00:10:46 +08:00
2016-01-28 05:45:23 +08:00
## Set default
if test "X-$SYMBOLS" = X- ; then
if test "X-$BUILD_MODE" = "X-debug" ; then
SYMBOLS=yes
else
SYMBOLS=no
fi
2007-04-27 22:56:33 +08:00
fi
2016-01-28 05:45:23 +08:00
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([SYMBOLS])
case "X-$SYMBOLS" in
2007-04-27 22:56:33 +08:00
X-yes)
2016-01-28 05:45:23 +08:00
H5_CFLAGS="$H5_CFLAGS $SYMBOLS_CFLAGS"
H5_CXXFLAGS="$H5_CXXFLAGS $SYMBOLS_CXXFLAGS"
H5_FCFLAGS="$H5_FCFLAGS $SYMBOLS_FCFLAGS"
AC_MSG_RESULT([yes])
;;
X-no)
2016-02-17 09:09:04 +08:00
H5_CFLAGS="$H5_CFLAGS $NO_SYMBOLS_CFLAGS"
H5_CXXFLAGS="$H5_CXXFLAGS $NO_SYMBOLS_CXXFLAGS"
H5_FCFLAGS="$H5_FCFLAGS $NO_SYMBOLS_FCFLAGS"
2016-01-28 05:45:23 +08:00
AC_MSG_RESULT([no])
2001-09-18 06:47:02 +08:00
;;
2016-01-28 05:45:23 +08:00
*)
H5_CFLAGS="$H5_CFLAGS $SYMBOLS"
H5_CXXFLAGS="$H5_CXXFLAGS $SYMBOLS"
H5_FCFLAGS="$H5_FCFLAGS $SYMBOLS"
SYMBOLS="custom ($SYMBOLS)"
AC_MSG_RESULT([$SYMBOLS])
2001-09-18 06:47:02 +08:00
;;
2016-01-28 05:45:23 +08:00
esac
## ----------------------------------------------------------------------
## Check if the assert macro should be enabled
##
AC_MSG_CHECKING([enable asserts])
AC_ARG_ENABLE([asserts],
[AS_HELP_STRING([--enable-asserts],
[Determines whether NDEBUG is defined or not, which
controls assertions.
This is independent of the build mode and presence
of debugging symbols.
[default=yes if debug build, otherwise no]
])],
[ASSERTS=$enableval])
## Set default
if test "X-$ASSERTS" = X- ; then
if test "X-$BUILD_MODE" = "X-debug" ; then
ASSERTS=yes
else
ASSERTS=no
fi
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([ASSERTS])
case "X-$ASSERTS" in
X-yes)
H5_CPPFLAGS="$H5_CPPFLAGS -UNDEBUG"
AC_MSG_RESULT([yes])
;;
X-no)
H5_CPPFLAGS="$H5_CPPFLAGS -DNDEBUG"
AC_MSG_RESULT([no])
;;
*)
AC_MSG_ERROR([Unrecognized value: $ASSERTS])
;;
esac
2017-01-11 02:49:49 +08:00
## ----------------------------------------------------------------------
## Check if developer warnings should be turned on
## These are warnings that provide suggestions like gcc's -Wsuggest-attribute.
## They do not indicate code problems.
##
## Note that developers don't need to build with these regularly. They
## are just handy to check once in a while (before releases, etc.).
##
AC_MSG_CHECKING([enable developer warnings])
AC_ARG_ENABLE([developer-warnings],
[AS_HELP_STRING([--enable-developer-warnings],
[Determines whether developer warnings will be
emitted. These are usually performance suggestions
(e.g. -Wsuggest-attribute) and do not flag poor code
quality.
[default=no]
])],
[DEV_WARNINGS=$enableval])
## Set default
if test "X-$DEV_WARNINGS" = X- ; then
DEV_WARNINGS=no
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([DEV_WARNINGS])
case "X-$DEV_WARNINGS" in
X-yes)
H5_CFLAGS="$H5_CFLAGS $DEVELOPER_WARNING_CFLAGS"
AC_MSG_RESULT([yes])
;;
X-no)
H5_CFLAGS="$H5_CFLAGS $NO_DEVELOPER_WARNING_CFLAGS"
AC_MSG_RESULT([no])
;;
*)
AC_MSG_ERROR([Unrecognized value: $DEV_WARNINGS])
;;
esac
2016-01-28 05:45:23 +08:00
## ----------------------------------------------------------------------
## Check if the compiler should use profiling flags/settings
##
AC_MSG_CHECKING([profiling])
AC_ARG_ENABLE([profiling],
[AS_HELP_STRING([--enable-profiling=(yes|no|<custom>)],
[Enable profiling flags (e.g.: -pg).
This can be set independently from the build mode.
The custom setting can be used to pass alternative
profiling flags (e.g.: -P for using Prof with gcc).
[default=no]
])],
[PROFILING=$enableval])
## Default is no profiling
if test "X-$PROFILING" = X- ; then
PROFILING=no
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([PROFILING])
case "X-$PROFILING" in
X-yes)
H5_CFLAGS="$H5_CFLAGS $PROFILE_CFLAGS"
H5_CXXFLAGS="$H5_CXXFLAGS $PROFILE_CXXFLAGS"
H5_FCFLAGS="$H5_FCFLAGS $PROFILE_FCFLAGS"
AC_MSG_RESULT([yes])
;;
X-no)
AC_MSG_RESULT([no])
;;
*)
H5_CFLAGS="$H5_CFLAGS $PROFILING"
H5_CXXFLAGS="$H5_CXXFLAGS $PROFILING"
H5_FCFLAGS="$H5_FCFLAGS $PROFILING"
PROFILING="custom ($PROFILING)"
AC_MSG_RESULT([$PROFILING])
;;
esac
## ----------------------------------------------------------------------
## Check if the compiler should use a particular optimization setting
##
AC_MSG_CHECKING([optimization level])
AC_ARG_ENABLE([optimization],
[AS_HELP_STRING([--enable-optimization=(high|debug|none|<custom>)],
[Enable optimization flags/settings (e.g.: -O3).
This can be set independently from the build mode.
Optimizations for a given compiler can be specified
at several levels: High, with aggressive optimizations
turned on; debug, with optimizations that are
unlikely to interfere with debugging or profiling;
2016-03-01 22:50:49 +08:00
and none, with no optimizations at all.
2016-01-28 05:45:23 +08:00
See the compiler-specific config/*-flags file for more
details.
Alternatively, optimization options can
be specified directly by specifying them as a
string value. These custom optimzation flags will
completely replace all other optimization flags.
[default depends on build mode: debug=debug,
production=high, clean=none]
])],
[OPTIMIZATION=$enableval])
## Set the default optimization level. This depends on the compiler mode.
if test "X-$OPTIMIZATION" = X- ; then
case "X-$BUILD_MODE" in
X-debug)
OPTIMIZATION=debug
;;
X-production)
OPTIMIZATION=high
;;
X-clean)
OPTIMIZATION=none
;;
esac
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([OPTIMIZATION])
case "X-$OPTIMIZATION" in
X-high)
H5_CFLAGS="$H5_CFLAGS $HIGH_OPT_CFLAGS"
2016-02-17 10:16:27 +08:00
H5_CXXFLAGS="$H5_CXXFLAGS $HIGH_OPT_CXXFLAGS"
2016-01-28 05:45:23 +08:00
H5_FCFLAGS="$H5_FCFLAGS $HIGH_OPT_FCFLAGS"
AC_MSG_RESULT([high])
;;
X-debug)
H5_CFLAGS="$H5_CFLAGS $DEBUG_OPT_CFLAGS"
2016-02-17 10:16:27 +08:00
H5_CXXFLAGS="$H5_CXXFLAGS $DEBUG_OPT_CXXFLAGS"
2016-01-28 05:45:23 +08:00
H5_FCFLAGS="$H5_FCFLAGS $DEBUG_OPT_FCFLAGS"
AC_MSG_RESULT([debug])
;;
X-none)
H5_CFLAGS="$H5_CFLAGS $NO_OPT_CFLAGS"
2016-02-17 10:16:27 +08:00
H5_CXXFLAGS="$H5_CXXFLAGS $NO_OPT_CXXFLAGS"
2016-01-28 05:45:23 +08:00
H5_FCFLAGS="$H5_FCFLAGS $NO_OPT_FCFLAGS"
2003-08-09 02:28:03 +08:00
AC_MSG_RESULT([none])
2001-09-18 06:47:02 +08:00
;;
*)
2016-01-28 05:45:23 +08:00
H5_CFLAGS="$H5_CFLAGS $OPTIMIZATION"
2016-02-17 10:16:27 +08:00
H5_CXXFLAGS="$H5_CXXFLAGS $OPTIMIZATION"
2016-01-28 05:45:23 +08:00
H5_FCFLAGS="$H5_FCFLAGS $OPTIMIZATION"
OPTIMIZATION="custom ($OPTIMIZATION)"
AC_MSG_RESULT([$OPTIMIZATION])
;;
esac
## ----------------------------------------------------------------------
## Enable/disable internal package-level debugging output
##
AC_MSG_CHECKING([for internal debug output])
AC_ARG_ENABLE([internal-debug],
[AS_HELP_STRING([--enable-internal-debug=(yes|all|no|none|<pkg list>)],
[Enable extra debugging output on HDF5 library
errors. One may also specify a comma-separated
list of package names without the leading H5.
This is independent of the build mode
and is mainly of interest to HDF Group developers.
Yes/all and no/none are synonymous.
[default=all if debug build, otherwise none]
])],
[INTERNAL_DEBUG_OUTPUT=$enableval])
## Set default
if test "X-$INTERNAL_DEBUG_OUTPUT" = X- ; then
if test "X-$BUILD_MODE" = "X-debug" ; then
INTERNAL_DEBUG_OUTPUT=all
else
INTERNAL_DEBUG_OUTPUT=none
fi
fi
AC_SUBST([INTERNAL_DEBUG_OUTPUT])
## These are all the packages that use H5*_DEBUG.
## There is no harm in specifying a package not in this list;
## you'll just get an unused H5<pkg>_DEBUG symbol.
2016-02-12 22:42:15 +08:00
##
## Some packages that define debug checks or output are
## too specialized or have huge performance hits. These
## are not listed in the "all" packages list.
##
2016-01-28 05:45:23 +08:00
## all_packages="AC,B,B2,D,F,FA,FL,FS,HL,I,O,S,ST,T,Z"
2016-02-12 22:42:15 +08:00
all_packages="AC,B2,D,F,HL,I,O,S,ST,T,Z"
2016-01-28 05:45:23 +08:00
case "X-$INTERNAL_DEBUG_OUTPUT" in
X-yes|X-all)
INTERNAL_DEBUG_OUTPUT=$all_packages
DEBUG_PKG_LIST=$all_packages
;;
X-no|X-none)
INTERNAL_DEBUG_OUTPUT=none
DEBUG_PKG_LIST=
;;
*)
DEBUG_PKG_LIST=$INTERNAL_DEBUG_OUTPUT
2001-09-18 06:47:02 +08:00
;;
2000-03-31 05:33:24 +08:00
esac
2016-01-28 05:45:23 +08:00
AC_MSG_RESULT([$INTERNAL_DEBUG_OUTPUT])
1998-04-03 11:29:38 +08:00
2016-01-28 05:45:23 +08:00
## Define H5*_DEBUG symbols that control package output
## NOTE: No sanity checking done here!
if test -n "$DEBUG_PKG_LIST"; then
for pkg in `echo $DEBUG_PKG_LIST | ${TR} ${as_cr_letters}"," ${as_cr_LETTERS}" "`; do
2006-04-26 05:19:14 +08:00
H5_CPPFLAGS="$H5_CPPFLAGS -DH5${pkg}_DEBUG"
2001-09-18 06:47:02 +08:00
done
1998-04-03 11:29:38 +08:00
fi
1997-08-16 00:35:53 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if they would like the function stack support compiled in
##
2003-06-26 10:08:36 +08:00
AC_MSG_CHECKING([whether function stack tracking is enabled])
2006-05-02 11:17:49 +08:00
AC_ARG_ENABLE([codestack],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-codestack],
2016-01-28 05:45:23 +08:00
[Enable the function stack tracing (for developer debugging).
[default=no]
])],
2006-05-02 11:17:49 +08:00
[CODESTACK=$enableval])
2003-06-26 10:08:36 +08:00
2016-01-28 05:45:23 +08:00
## Set the default level.
if test "X-$CODESTACK" = X- ; then
CODESTACK=no
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([CODESTACK])
2006-05-02 11:17:49 +08:00
case "X-$CODESTACK" in
2006-03-23 02:44:55 +08:00
X-yes)
2003-06-26 10:08:36 +08:00
AC_MSG_RESULT([yes])
2006-05-02 11:17:49 +08:00
AC_DEFINE([HAVE_CODESTACK], [1],
2003-06-26 10:08:36 +08:00
[Define if the function stack tracing code is to be compiled in])
;;
2016-01-28 05:45:23 +08:00
X-no)
2003-06-26 10:08:36 +08:00
AC_MSG_RESULT([no])
;;
2016-01-28 05:45:23 +08:00
*)
AC_MSG_ERROR([Unrecognized value: $CODESTACK])
;;
2003-06-26 10:08:36 +08:00
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if they would like the metadata trace file code compiled in
##
2006-07-14 01:59:39 +08:00
AC_MSG_CHECKING([whether metadata trace file code is enabled])
AC_ARG_ENABLE([metadata-trace-file],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-metadata-trace-file],
2016-01-28 05:45:23 +08:00
[Enable metadata trace file collection.
[default=no]
])],
2006-07-14 01:59:39 +08:00
[METADATATRACEFILE=$enableval])
2016-01-28 05:45:23 +08:00
## Set the default level.
if test "X-$METADATATRACEFILE" = X- ; then
METADATATRACEFILE=no
fi
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([METADATATRACEFILE])
2006-07-14 01:59:39 +08:00
case "X-$METADATATRACEFILE" in
X-yes)
AC_MSG_RESULT([yes])
AC_DEFINE([METADATA_TRACE_FILE], [1],
[Define if the metadata trace file code is to be compiled in])
;;
2016-01-28 05:45:23 +08:00
X-no)
2006-07-14 01:59:39 +08:00
AC_MSG_RESULT([no])
;;
2016-01-28 05:45:23 +08:00
*)
AC_MSG_ERROR([Unrecognized value: $METADATATRACEFILE])
;;
2006-07-14 01:59:39 +08:00
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Enable tracing of the API
##
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([for API tracing]);
2002-07-18 00:10:46 +08:00
AC_ARG_ENABLE([trace],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-trace],
2016-01-28 05:45:23 +08:00
[Enable HDF5 API tracing capability.
[default=yes if debug build, otherwise no]
])],
[TRACE_API=$enableval])
## Set the default level.
if test "X-$TRACE_API" = X- ; then
if test "X-$BUILD_MODE" = "X-debug" ; then
TRACE_API=yes
2002-08-20 04:28:05 +08:00
else
2016-01-28 05:45:23 +08:00
TRACE_API=no
2002-08-20 04:28:05 +08:00
fi
1998-07-09 02:41:04 +08:00
fi
2003-07-29 05:38:04 +08:00
2016-01-28 05:45:23 +08:00
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([TRACE_API])
case "X-$TRACE_API" in
2002-08-20 04:28:05 +08:00
X-yes)
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([yes])
2006-04-26 05:19:14 +08:00
H5_CPPFLAGS="$H5_CPPFLAGS -DH5_DEBUG_API"
2002-08-20 04:28:05 +08:00
;;
2016-01-28 05:45:23 +08:00
X-no)
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([no])
2006-04-26 05:19:14 +08:00
H5_CPPFLAGS="$H5_CPPFLAGS -UH5_DEBUG_API"
2002-08-20 04:28:05 +08:00
;;
2016-01-28 05:45:23 +08:00
*)
AC_MSG_ERROR([Unrecognized value: $TRACE_API])
2004-07-23 04:46:27 +08:00
;;
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if they would like to use a memory checking tool (like valgrind's
## 'memcheck' tool, or Rational Purify, etc) and the library should be
## more scrupulous with it's memory operations. Enabling this also
## disables the library's free space manager code.
##
2007-05-30 04:02:34 +08:00
AC_MSG_CHECKING([whether a memory checking tool will be used])
AC_ARG_ENABLE([using-memchecker],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-using-memchecker],
2007-05-30 04:02:34 +08:00
[Enable this option if a memory allocation and/or
bounds checking tool will be used on the HDF5
library. Enabling this causes the library to be
2016-01-28 05:45:23 +08:00
more picky about its memory operations and also
2007-05-30 04:02:34 +08:00
disables the library's free space manager code.
2016-01-04 06:06:52 +08:00
This option is orthogonal to the
--enable-memory-alloc-sanity-check option.
2016-01-28 05:45:23 +08:00
[default=no]
])],
2007-05-30 04:02:34 +08:00
[USINGMEMCHECKER=$enableval])
2016-01-28 05:45:23 +08:00
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([USINGMEMCHECKER])
## Set the default level.
if test "X-$USINGMEMCHECKER" = X- ; then
USINGMEMCHECKER=no
fi
2007-05-30 04:02:34 +08:00
case "X-$USINGMEMCHECKER" in
X-yes)
AC_DEFINE([USING_MEMCHECKER], [1],
[Define if a memory checking tool will be used on the library,
to cause library to be very picky about memory operations and
also disable the internal free list manager code.])
2016-01-28 05:45:23 +08:00
AC_MSG_RESULT([yes])
2007-05-30 04:02:34 +08:00
;;
2016-01-28 05:45:23 +08:00
X-no)
2007-05-30 04:02:34 +08:00
AC_MSG_RESULT([no])
;;
2016-01-28 05:45:23 +08:00
*)
AC_MSG_ERROR([Unrecognized value: $USINGMEMCHECKER])
;;
2007-05-30 04:02:34 +08:00
esac
2016-01-04 06:06:52 +08:00
## ----------------------------------------------------------------------
## Check if they would like to enable the internal memory allocation sanity
## checking code.
##
AC_MSG_CHECKING([whether internal memory allocation sanity checking is used])
AC_ARG_ENABLE([memory-alloc-sanity-check],
[AS_HELP_STRING([--enable-memory-alloc-sanity-check],
[Enable this option to turn on internal memory
allocation sanity checking. This could cause
more memory use and somewhat slower allocation.
This option is orthogonal to the
--enable-using-memchecker option.
2016-01-28 05:45:23 +08:00
[default=yes if debug build, otherwise no]
])],
2016-01-04 06:06:52 +08:00
[MEMORYALLOCSANITYCHECK=$enableval])
2016-01-28 05:45:23 +08:00
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([MEMORYALLOCSANITYCHECK])
## Set default
if test "X-$MEMORYALLOCSANITYCHECK" = X- ; then
if test "X-$BUILD_MODE" = "X-debug" ; then
MEMORYALLOCSANITYCHECK=yes
else
MEMORYALLOCSANITYCHECK=no
fi
fi
2016-01-04 06:06:52 +08:00
case "X-$MEMORYALLOCSANITYCHECK" in
X-yes)
AC_DEFINE([MEMORY_ALLOC_SANITY_CHECK], [1],
[Define to enable internal memory allocation sanity checking.])
2016-01-28 05:45:23 +08:00
AC_MSG_RESULT([yes])
2016-01-04 06:06:52 +08:00
;;
2016-01-28 05:45:23 +08:00
X-no)
2016-01-04 06:06:52 +08:00
AC_MSG_RESULT([no])
;;
2016-01-28 05:45:23 +08:00
*)
AC_MSG_ERROR([Unrecognized value: $MEMORYALLOCSANITYCHECK])
;;
2016-01-04 06:06:52 +08:00
esac
2012-09-12 04:11:44 +08:00
## Checkpoint the cache
2000-04-21 02:41:51 +08:00
AC_CACHE_SAVE
2012-09-12 04:11:44 +08:00
## What header files and libraries do we have to look for for parallel
## support? For the most part, search paths are already specified with
2015-02-17 00:17:03 +08:00
## CPPFLAGS and LDFLAGS or are known to the compiler.
2012-09-12 04:11:44 +08:00
##
2002-07-18 00:10:46 +08:00
AC_ARG_ENABLE([parallel],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-parallel],
2002-07-18 00:10:46 +08:00
[Search for MPI-IO and MPI support files])])
1999-03-04 07:17:48 +08:00
2012-09-12 04:11:44 +08:00
## The --enable-parallel flag is not compatible with --enable-cxx.
## If the user tried to specify both flags, throw an error, unless
## they also provided the --enable-unsupported flag.
2010-11-18 02:07:51 +08:00
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${HDF_CXX}" = "Xyes" -a "X${enable_parallel}" = "Xyes"; then
AC_MSG_ERROR([--enable-cxx and --enable-parallel flags are incompatible. Use --enable-unsupported to override this error.])
fi
2005-09-02 04:31:46 +08:00
fi
2016-03-22 16:03:50 +08:00
## The --enable-parallel flag is not compatible with --enable-java.
## If the user tried to specify both flags, throw an error, unless
## they also provided the --enable-unsupported flag.
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${HDF_JAVA}" = "Xyes" -a "X${enable_parallel}" = "Xyes"; then
AC_MSG_ERROR([--enable-java and --enable-parallel flags are incompatible. Use --enable-unsupported to override this error.])
fi
fi
2012-09-12 04:11:44 +08:00
## --enable-parallel is also incompatible with --enable-threadsafe, unless
## --enable-unsupported has been specified on the configure line.
2010-11-18 02:07:51 +08:00
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${THREADSAFE}" = "Xyes" -a "X${enable_parallel}" = "Xyes"; then
AC_MSG_ERROR([--enable-threadsafe and --enable-parallel flags are incompatible. Use --enable-unsupported to override this error.])
fi
2005-09-02 04:31:46 +08:00
fi
2002-07-18 00:10:46 +08:00
AC_MSG_CHECKING([for parallel support files])
1999-03-04 07:17:48 +08:00
case "X-$enable_parallel" in
2001-09-28 07:05:16 +08:00
X-|X-no|X-none)
2015-02-17 00:17:03 +08:00
## We are not compiling for parallel.
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([skipped])
2001-09-28 07:05:16 +08:00
;;
2000-09-15 06:19:24 +08:00
2001-09-28 07:05:16 +08:00
X-yes)
2012-09-12 04:11:44 +08:00
## We want to compile a parallel library with a compiler that
## may already know how to link with MPI and MPI-IO.
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([provided by compiler])
2001-09-28 07:05:16 +08:00
PARALLEL=yes
2015-02-17 00:17:03 +08:00
## Try link a simple MPI program.
AC_MSG_CHECKING([whether a simple MPI-IO C program can be linked])
AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include <mpi.h>]],
2016-03-01 22:50:49 +08:00
[[ MPI_Init(0, (void *)0);
MPI_File_open(0, (void *)0, 0, 0, (void *)0);]])],
[AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])
AC_MSG_ERROR([unable to link a simple MPI-IO C program])])
2003-07-29 05:38:04 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
2015-02-17 01:17:49 +08:00
PAC_PROG_FC_MPI_CHECK
2001-09-28 07:05:16 +08:00
fi
2012-09-12 04:11:44 +08:00
## Set RUNPARALLEL to mpiexec if not set yet.
2001-09-28 07:05:16 +08:00
if test "X$PARALLEL" = "Xyes" -a -z "$RUNPARALLEL"; then
2010-10-29 01:19:30 +08:00
RUNPARALLEL="mpiexec -n \$\${NPROCS:=6}"
2001-09-28 07:05:16 +08:00
fi
;;
*)
2003-07-29 05:38:04 +08:00
AC_MSG_RESULT([error])
AC_MSG_ERROR([\'$enable_parallel\' is not a valid parallel search type])
2001-09-28 07:05:16 +08:00
;;
1999-03-04 07:17:48 +08:00
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Print some other parallel information and do some sanity checks.
2016-01-28 05:45:23 +08:00
## Needs to be done outside of the PARALLEL block since the serial
## build also needs to have values defined.
2012-09-12 04:11:44 +08:00
##
2003-07-29 05:38:04 +08:00
AC_SUBST([ADD_PARALLEL_FILES]) ADD_PARALLEL_FILES="no"
2016-01-28 05:45:23 +08:00
AC_SUBST([MPE]) MPE=no
AC_SUBST([INSTRUMENT_LIBRARY]) INSTRUMENT_LIBRARY=no
2003-07-29 05:38:04 +08:00
2000-09-15 06:19:24 +08:00
if test -n "$PARALLEL"; then
2012-09-12 04:11:44 +08:00
## The 'testpar' directory should participate in the build
2001-09-28 07:05:16 +08:00
TESTPARALLEL=testpar
1999-03-04 07:17:48 +08:00
2012-09-12 04:11:44 +08:00
## We are building a parallel library
2003-07-29 05:38:04 +08:00
AC_DEFINE([HAVE_PARALLEL], [1], [Define if we have parallel support])
2001-09-28 07:05:16 +08:00
2012-09-12 04:11:44 +08:00
## Display what we found about running programs
2003-07-29 05:38:04 +08:00
AC_MSG_CHECKING([prefix for running on one processor])
AC_MSG_RESULT([$RUNSERIAL])
AC_MSG_CHECKING([prefix for running in parallel])
AC_MSG_RESULT([$RUNPARALLEL])
2001-09-28 07:05:16 +08:00
2012-09-12 04:11:44 +08:00
## There *must* be some way to run in parallel even if it's just the
## word `none'.
2001-09-28 07:05:16 +08:00
if test -z "$RUNPARALLEL"; then
2003-07-29 05:38:04 +08:00
AC_MSG_ERROR([no way to run a parallel program])
2001-09-28 07:05:16 +08:00
fi
2012-09-12 04:11:44 +08:00
## If RUNSERIAL or RUNPARALLEL is the word `none' then replace it with
2015-06-17 05:25:03 +08:00
## the empty string. This means that no launch commands were requested,
2015-02-17 00:17:03 +08:00
## so we will not use any launch commands.
2001-09-28 07:05:16 +08:00
if test "X$RUNSERIAL" = "Xnone"; then
RUNSERIAL=""
fi
if test "X$RUNPARALLEL" = "Xnone"; then
RUNPARALLEL=""
fi
2003-07-29 05:38:04 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
ADD_PARALLEL_FILES="yes"
AC_MSG_CHECKING([for MPI_Comm_c2f and MPI_Comm_f2c functions])
2015-09-19 20:24:40 +08:00
AC_LINK_IFELSE([AC_LANG_PROGRAM([[
#include <mpi.h>
]],
[[MPI_Comm c_comm; MPI_Comm_c2f(c_comm)]])],
[AC_DEFINE([HAVE_MPI_MULTI_LANG_Comm], [1],
[Define if MPI_Comm_c2f and MPI_Comm_f2c exist])
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])]
2003-07-29 05:38:04 +08:00
)
AC_MSG_CHECKING([for MPI_Info_c2f and MPI_Info_f2c functions])
2015-09-19 20:24:40 +08:00
AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include <mpi.h>]],
[[MPI_Info c_info; MPI_Info_c2f(c_info)]])],
[AC_DEFINE([HAVE_MPI_MULTI_LANG_Info], [1],
[Define if MPI_Info_c2f and MPI_Info_f2c exist])
AC_MSG_RESULT([yes])],
[AC_MSG_RESULT([no])]
2003-07-29 05:38:04 +08:00
)
fi
2016-01-28 05:45:23 +08:00
## ----------------------------------------------------------------------
## Enable instrumenting of the library's internal operations
## in parallel builds.
##
## Set default
if test "X-$BUILD_MODE" = "X-debug" ; then
INSTRUMENT_LIBRARY=yes
else
INSTRUMENT_LIBRARY=no
fi
AC_MSG_CHECKING([for instrumented library]);
AC_ARG_ENABLE([instrument],
[AS_HELP_STRING([--enable-instrument],
[Enable library instrumentation of optimization
tracing (only used with parallel builds).
[default=yes if a parallel debug build, otherwise no]
])],
[INSTRUMENT_LIBRARY=$enableval])
## Allow this variable to be substituted in
## other files (src/libhdf5.settings.in, etc.)
AC_SUBST([INSTRUMENT_LIBRARY])
case "X-$INSTRUMENT_LIBRARY" in
X-yes)
AC_DEFINE([HAVE_INSTRUMENTED_LIBRARY], [1],
[Define if parallel library will contain instrumentation to detect correct optimization operation])
AC_MSG_RESULT([yes])
;;
X-no)
AC_MSG_RESULT([no])
;;
*)
AC_MSG_ERROR([Unrecognized value: $INSTRUMENT_LIBRARY])
;;
esac
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------
## Do we want MPE instrumentation feature on?
##
## This must be done after enable-parallel is checked since it depends
## on a mpich compiler.
##
2008-05-15 13:12:00 +08:00
MPE=yes
2003-06-24 23:34:27 +08:00
AC_ARG_WITH([mpe],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--with-mpe=DIR],
2003-06-24 23:34:27 +08:00
[Use MPE instrumentation [default=no]])],,
[withval=no])
case "X-$withval" in
X-|X-no|X-none)
AC_MSG_CHECKING([for MPE])
AC_MSG_RESULT([suppressed])
unset MPE
;;
X-yes)
AC_CHECK_HEADERS([mpe.h],, [unset MPE])
AC_CHECK_LIB([mpe], [MPE_Init_log],, [unset MPE])
;;
*)
case "$withval" in
*,*)
mpe_inc="`echo $withval | cut -f1 -d,`"
mpe_lib="`echo $withval | cut -f2 -d, -s`"
;;
*)
if test -n "$withval"; then
mpe_inc="$withval/include"
mpe_lib="$withval/lib"
fi
;;
esac
2015-06-17 05:25:03 +08:00
2003-06-24 23:34:27 +08:00
if test -n "$mpe_inc"; then
saved_CPPFLAGS="$CPPFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_CPPFLAGS="$AM_CPPFLAGS"
2003-06-24 23:34:27 +08:00
CPPFLAGS="$CPPFLAGS -I$mpe_inc"
2009-10-15 05:43:05 +08:00
AM_CPPFLAGS="$AM_CPPFLAGS -I$mpe_inc"
AC_CHECK_HEADERS([mpe.h],, [CPPFLAGS="$saved_CPPFLAGS"; AM_CPPFLAGS="$saved_AM_CPPFLAGS"; unset MPE])
2003-06-24 23:34:27 +08:00
else
AC_CHECK_HEADERS([mpe.h],, [unset MPE])
fi
2015-06-17 05:25:03 +08:00
2003-06-24 23:34:27 +08:00
if test -n "$mpe_lib"; then
saved_LDFLAGS="$LDFLAGS"
2009-10-15 05:43:05 +08:00
saved_AM_LDFLAGS="$AM_LDFLAGS"
2003-06-24 23:34:27 +08:00
LDFLAGS="$LDFLAGS -L$mpe_lib"
2009-10-15 05:43:05 +08:00
AM_LDFLAGS="$AM_LDFLAGS -L$mpe_lib"
2003-06-24 23:34:27 +08:00
AC_CHECK_LIB([mpe], [MPE_Init_log],,
2009-10-15 05:43:05 +08:00
[LDFLAGS="$saved_LDFLAGS"; AM_LDFLAGS="$saved_AM_LDFLAGS"; unset MPE])
2003-06-24 23:34:27 +08:00
else
AC_CHECK_LIB([mpe], [MPE_Init_log],, [unset MPE])
fi
;;
esac
if test "X-$MPE" = "X-yes"; then
AC_DEFINE([HAVE_MPE], [1], [Define if we have MPE support])
fi
2003-09-17 01:33:00 +08:00
fi
2004-06-09 21:47:20 +08:00
2015-03-04 08:27:40 +08:00
## ----------------------------------------------------------------------
## Check if Direct I/O driver is enabled by --enable-direct-vfd
##
2016-01-28 05:45:23 +08:00
AC_SUBST([DIRECT_VFD])
## Default is no direct VFD
DIRECT_VFD=no
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
AC_CACHE_VAL([hdf5_cv_direct_io],
AC_CHECK_DECL([O_DIRECT], [hdf5_cv_direct_io=yes], [hdf5_cv_direct_io=no], [[#include <fcntl.h>]]))
AC_CACHE_VAL([hdf5_cv_posix_memalign],
AC_CHECK_FUNC([posix_memalign], [hdf5_cv_posix_memalign=yes], [hdf5_cv_posix_memalign=no]))
AC_MSG_CHECKING([if the direct I/O virtual file driver (VFD) is enabled])
2006-10-11 04:07:16 +08:00
AC_ARG_ENABLE([direct-vfd],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-direct-vfd],
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
[Build the direct I/O virtual file driver (VFD).
This is based on the POSIX (sec2) VFD and
requires the open() call to take the O_DIRECT
flag. [default=no]])],
[DIRECT_VFD=$enableval], [DIRECT_VFD=no])
if test "X$DIRECT_VFD" = "Xyes"; then
if test ${hdf5_cv_direct_io} = "yes" && test ${hdf5_cv_posix_memalign} = "yes" ; then
AC_MSG_RESULT([yes])
AC_DEFINE([HAVE_DIRECT], [1],
[Define if the direct I/O virtual file driver (VFD) should be compiled])
else
AC_MSG_RESULT([no])
DIRECT_VFD=no
AC_MSG_ERROR([The direct VFD was requested but cannot be built. This is either
due to O_DIRECT not being found in fcntl.h or a lack of
posix_memalign() on your system. Please re-configure without
specifying --enable-direct-vfd.])
fi
2006-10-11 04:07:16 +08:00
else
[svn-r26275] Merge of r26042, 26083, 26084, 26085 from features/autotools_rework
- Updated configure.ac so that the direct VFD can now be built
without specifying _GNU_SOURCE, etc. on the command line.
- The direct VFD is now disabled by default. It was previously
enabled, but the configuration script couldn't configure it
properly, making it a moot point.
Fixes: HDFFV-9057, HDFFV-7567, HDFFV-9088, HDFFV-7566
Tested on: h5committest
jam w/ direct VFD (*very* slow!)
NOTE: platypus cmake fails, but this is not a new error.
2015-02-22 23:09:26 +08:00
AC_MSG_RESULT([no])
2006-10-11 04:07:16 +08:00
fi
2006-10-11 04:47:24 +08:00
2016-01-28 05:45:23 +08:00
## Direct VFD files are not built if not required.
2006-10-11 04:47:24 +08:00
AM_CONDITIONAL([DIRECT_VFD_CONDITIONAL], [test "X$DIRECT_VFD" = "Xyes"])
2006-11-07 06:17:46 +08:00
2013-09-20 00:38:08 +08:00
## ----------------------------------------------------------------------
## Enable custom plugin default path for library. It requires SHARED support.
##
AC_MSG_CHECKING([for custom plugin default path definition])
AC_ARG_WITH([default-plugindir],
[AS_HELP_STRING([--with-default-plugindir=location],
[Specify default location for plugins
[default="/usr/local/hdf5/lib/plugin"]])],,
withval="/usr/local/hdf5/lib/plugin")
if test "X$withval" = "X"; then
AC_MSG_RESULT([default])
default_plugindir="/usr/local/hdf5/lib/plugin"
else
AC_MSG_RESULT([$withval])
default_plugindir=$withval
fi
AC_DEFINE_UNQUOTED([DEFAULT_PLUGINDIR], ["$default_plugindir"],
[Define the default plugins path to compile])
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Decide whether the presence of user's exception handling functions is
## checked and data conversion exceptions are returned. This is mainly
## for the speed optimization of hard conversions. Soft conversions can
2015-06-17 05:25:03 +08:00
## actually benefit little.
2012-09-12 04:11:44 +08:00
##
2005-08-29 23:21:58 +08:00
AC_MSG_CHECKING([whether exception handling functions is checked during data conversions])
2005-08-30 23:11:08 +08:00
AC_ARG_ENABLE([dconv-exception],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-dconv-exception],
2015-06-17 05:25:03 +08:00
[if exception handling functions is checked during
2005-08-29 23:21:58 +08:00
data conversions [default=yes]])],
2005-09-02 02:48:00 +08:00
[DCONV_EXCEPTION=$enableval], [DCONV_EXCEPTION=yes])
2005-08-29 23:21:58 +08:00
if test "$DCONV_EXCEPTION" = "yes"; then
AC_MSG_RESULT([yes])
AC_DEFINE([WANT_DCONV_EXCEPTION], [1],
[Check exception handling functions during data conversions])
else
AC_MSG_RESULT([no])
fi
2015-07-24 15:04:52 +08:00
## ----------------------------------------------------------------------
## Decide whether the data accuracy has higher priority during data
## conversions. If not, some hard conversions will still be prefered even
2016-03-01 22:50:49 +08:00
## though the data may be wrong (for example, some compilers don't
2015-07-24 15:04:52 +08:00
## support denormalized floating values) to maximize speed.
2016-03-01 22:50:49 +08:00
##
2015-07-24 15:04:52 +08:00
AC_MSG_CHECKING([whether data accuracy is guaranteed during data conversions])
AC_ARG_ENABLE([dconv-accuracy],
[AS_HELP_STRING([--enable-dconv-accuracy],
2016-03-01 22:50:49 +08:00
[if data accuracy is guaranteed during
2015-07-24 15:04:52 +08:00
data conversions [default=yes]])],
[DATA_ACCURACY=$enableval], [DATA_ACCURACY=yes])
if test "$DATA_ACCURACY" = "yes"; then
AC_MSG_RESULT([yes])
AC_DEFINE([WANT_DATA_ACCURACY], [1],
[Data accuracy is prefered to speed during data conversions])
else
AC_MSG_RESULT([no])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Set the flag to indicate that the machine has window style pathname,
## that is, "drive-letter:\" (e.g. "C:") or "drive-letter:/" (e.g. "C:/").
## (This flag should be _unset_ for all machines, except for Windows, where
## it's set in the custom Windows H5pubconf.h file)
##
2008-05-01 03:51:13 +08:00
AC_MSG_CHECKING([if the machine has window style path name])
2008-05-16 05:35:13 +08:00
case "`uname`" in
MINGW*)
AC_DEFINE([HAVE_WINDOW_PATH], [1],
[Define if your system has window style path name.])
AC_MSG_RESULT([yes])
;;
*)
AC_MSG_RESULT([no])
;;
esac
2008-05-01 03:51:13 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Set the flag to indicate that the machine is using a special algorithm to convert
2015-06-17 05:25:03 +08:00
## 'long double' to '(unsigned) long' values. (This flag should only be set for
## the IBM Power6 Linux. When the bit sequence of long double is
## 0x4351ccf385ebc8a0bfcc2a3c3d855620, the converted value of (unsigned)long
2012-09-12 04:11:44 +08:00
## is 0x004733ce17af227f, not the same as the library's conversion to 0x004733ce17af2282.
## The machine's conversion gets the correct value. We define the macro and disable
## this kind of test until we figure out what algorithm they use.
##
2010-10-29 03:08:31 +08:00
AC_MSG_CHECKING([if using special algorithm to convert long double to (unsigned) long values])
2016-07-19 02:37:17 +08:00
## NOTE: Place all configure test programs into cmake's source file, then use a preprocessor directive
## to select the proper test program. This is done by echoing the #define and cat'ing the cmake
## source file. (HDFFV-9467)
TEST_SRC="`(echo \"#define H5_LDOUBLE_TO_LONG_SPECIAL_TEST 1\"; cat $srcdir/config/cmake/ConversionTests.c)`"
2010-10-29 03:08:31 +08:00
if test ${ac_cv_sizeof_long_double} = 0; then
hdf5_cv_ldouble_to_long_special=${hdf5_cv_ldouble_to_long_special=no}
else
AC_CACHE_VAL([hdf5_cv_ldouble_to_long_special],
2015-03-28 03:33:41 +08:00
[AC_RUN_IFELSE(
2016-07-19 02:37:17 +08:00
[AC_LANG_SOURCE([$TEST_SRC])]
2015-03-28 03:33:41 +08:00
, [hdf5_cv_ldouble_to_long_special=yes], [hdf5_cv_ldouble_to_long_special=no],)])
2010-10-29 03:08:31 +08:00
fi
if test ${hdf5_cv_ldouble_to_long_special} = "yes"; then
AC_DEFINE([LDOUBLE_TO_LONG_SPECIAL], [1],
[Define if your system converts long double to (unsigned) long values with special algorithm.])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Set the flag to indicate that the machine is using a special algorithm
2015-06-17 05:25:03 +08:00
## to convert some values of '(unsigned) long' to 'long double' values.
## (This flag should be off for all machines, except for IBM Power6 Linux,
## when the bit sequences are 003fff..., 007fff..., 00ffff..., 01ffff...,
## ..., 7fffff..., the compiler uses a unknown algorithm. We define a
2012-09-12 04:11:44 +08:00
## macro and skip the test for now until we know about the algorithm.
##
2010-10-29 03:08:31 +08:00
AC_MSG_CHECKING([if using special algorithm to convert (unsigned) long to long double values])
2016-07-19 02:37:17 +08:00
TEST_SRC="`(echo \"#define H5_LONG_TO_LDOUBLE_SPECIAL_TEST 1\"; cat $srcdir/config/cmake/ConversionTests.c)`"
2010-10-29 03:08:31 +08:00
if test ${ac_cv_sizeof_long_double} = 0; then
hdf5_cv_long_to_ldouble_special=${hdf5_cv_long_to_ldouble_special=no}
else
AC_CACHE_VAL([hdf5_cv_long_to_ldouble_special],
2015-03-28 03:33:41 +08:00
[AC_RUN_IFELSE(
2016-07-19 02:37:17 +08:00
[AC_LANG_SOURCE([$TEST_SRC])]
2015-03-28 03:33:41 +08:00
, [hdf5_cv_long_to_ldouble_special=yes], [hdf5_cv_long_to_ldouble_special=no],)])
2010-10-29 03:08:31 +08:00
fi
if test ${hdf5_cv_long_to_ldouble_special} = "yes"; then
AC_DEFINE([LONG_TO_LDOUBLE_SPECIAL], [1],
[Define if your system can convert (unsigned) long to long double values with special algorithm.])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
2015-07-24 15:04:52 +08:00
## ----------------------------------------------------------------------
## Set the flag to indicate that the machine can accurately convert
## 'long double' to '(unsigned) long long' values. (This flag should
## be set for all machines, except for Mac OS 10.4, SGI IRIX64 6.5 and
## Powerpc Linux using XL compilers.
## When the bit sequence of long double is 0x4351ccf385ebc8a0bfcc2a3c...,
## the values of (unsigned)long long start to go wrong on these
## two machines. Adjusting it higher to 0x4351ccf385ebc8a0dfcc... or
## 0x4351ccf385ebc8a0ffcc... will make the converted values wildly wrong.
## This test detects this wrong behavior and disable the test.
##
AC_MSG_CHECKING([if correctly converting long double to (unsigned) long long values])
2016-07-19 02:37:17 +08:00
TEST_SRC="`(echo \"#define H5_LDOUBLE_TO_LLONG_ACCURATE_TEST 1\"; cat $srcdir/config/cmake/ConversionTests.c)`"
2015-07-24 15:04:52 +08:00
if test ${ac_cv_sizeof_long_double} = 0; then
hdf5_cv_ldouble_to_llong_accurate=${hdf5_cv_ldouble_to_llong_accurate=no}
else
AC_CACHE_VAL([hdf5_cv_ldouble_to_llong_accurate],
2016-11-03 23:58:43 +08:00
[AC_RUN_IFELSE([AC_LANG_SOURCE([$TEST_SRC])],
2016-07-19 02:37:17 +08:00
[hdf5_cv_ldouble_to_llong_accurate=yes], [hdf5_cv_ldouble_to_llong_accurate=no],[])])
2015-07-24 15:04:52 +08:00
fi
if test ${hdf5_cv_ldouble_to_llong_accurate} = "yes"; then
AC_DEFINE([LDOUBLE_TO_LLONG_ACCURATE], [1],
[Define if your system can convert long double to (unsigned) long long values correctly.])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
## ----------------------------------------------------------------------
## Set the flag to indicate that the machine can accurately convert
## '(unsigned) long long' to 'long double' values. (This flag should be
## set for all machines, except for Mac OS 10.4 and Powerpc Linux using
## XL compilers.
## When the bit sequences are 003fff..., 007fff..., 00ffff..., 01ffff...,
## ..., 7fffff..., the converted values are twice as big as they should be.
##
AC_MSG_CHECKING([if correctly converting (unsigned) long long to long double values])
2016-07-19 02:37:17 +08:00
TEST_SRC="`(echo \"#define H5_LLONG_TO_LDOUBLE_CORRECT_TEST 1\"; cat $srcdir/config/cmake/ConversionTests.c)`"
2015-07-24 15:04:52 +08:00
if test ${ac_cv_sizeof_long_double} = 0; then
hdf5_cv_llong_to_ldouble_correct=${hdf5_cv_llong_to_ldouble_correct=no}
else
AC_CACHE_VAL([hdf5_cv_llong_to_ldouble_correct],
2016-07-19 02:37:17 +08:00
[AC_RUN_IFELSE([AC_LANG_SOURCE([$TEST_SRC])],
[hdf5_cv_llong_to_ldouble_correct=yes], [hdf5_cv_llong_to_ldouble_correct=no],[])])
2015-07-24 15:04:52 +08:00
fi
if test ${hdf5_cv_llong_to_ldouble_correct} = "yes"; then
AC_DEFINE([LLONG_TO_LDOUBLE_CORRECT], [1],
[Define if your system can convert (unsigned) long long to long double values correctly.])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Set some variables for general configuration information to be saved
2015-03-21 03:01:59 +08:00
## and installed with the libraries (used to generate libhdf5.settings).
2012-09-12 04:11:44 +08:00
##
[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
2012-09-12 04:11:44 +08:00
## HDF5 version from the first line of the README.txt file.
2002-03-21 02:14:36 +08:00
H5_VERSION="`cut -d' ' -f3 $srcdir/README.txt | head -1`"
2003-07-29 05:38:04 +08:00
AC_SUBST([H5_VERSION])
[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
2012-09-12 04:11:44 +08:00
## Configuration date
2003-07-29 05:38:04 +08:00
AC_SUBST([CONFIG_DATE]) CONFIG_DATE="`date`"
[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
2012-09-12 04:11:44 +08:00
## User doing the configuration
2003-07-29 05:38:04 +08:00
AC_SUBST([CONFIG_USER]) CONFIG_USER="`whoami`@`hostname`"
2000-09-15 06:19:24 +08:00
if test -n "$ORGANIZATION"; then
2001-09-28 07:05:16 +08:00
CONFIG_USER="$CONFIG_USER at $ORGANIZATION"
[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
fi
2016-01-28 05:45:23 +08:00
## Configuration mode (production, debug, etc.) saved above.
2003-07-29 05:38:04 +08:00
AC_SUBST([CONFIG_MODE])
[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
2012-09-12 04:11:44 +08:00
## Byte sex from the AC_C_BIGENDIAN macro.
2003-07-29 05:38:04 +08:00
AC_SUBST([BYTESEX])
2000-09-15 06:19:24 +08:00
if test "X$ac_cv_c_bigendian" = "Xyes"; then
2001-09-28 07:05:16 +08:00
BYTESEX="big-endian"
2000-04-07 23:25:41 +08:00
else
2001-09-28 07:05:16 +08:00
BYTESEX="little-endian"
[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
fi
2009-02-27 04:21:50 +08:00
if test "X$ac_cv_c_bigendian" = "Xyes"; then
WORDS_BIGENDIAN="yes"
else
WORDS_BIGENDIAN="no"
fi
AC_SUBST([WORDS_BIGENDIAN])
2012-09-12 04:11:44 +08:00
## Parallel support? (set above except empty if none)
[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
PARALLEL=${PARALLEL:-no}
2012-09-12 04:11:44 +08:00
## Compiler with version information. This consists of the full path
## name of the compiler and the reported version number.
2003-07-29 05:38:04 +08:00
AC_SUBST([CC_VERSION])
2012-09-12 04:11:44 +08:00
## Strip anything that looks like a flag off of $CC
2005-03-04 03:39:10 +08:00
CC_NOFLAGS=`echo $CC | sed 's/ -.*//'`
if `echo $CC_NOFLAGS | grep ^/ >/dev/null 2>&1`; then
2005-03-02 02:47:23 +08:00
CC_VERSION="$CC"
2000-09-15 06:19:24 +08:00
else
2001-09-28 07:05:16 +08:00
CC_VERSION="$CC";
for x in `echo $PATH | sed -e 's/:/ /g'`; do
2008-05-14 00:43:42 +08:00
if test -x $x/$CC_NOFLAGS; then
2001-09-28 07:05:16 +08:00
CC_VERSION="$x/$CC"
break
fi
done
2000-11-16 22:50:38 +08:00
fi
2010-07-09 10:52:14 +08:00
if test -n "$cc_version_info"; then
CC_VERSION="$CC_VERSION ( $cc_version_info)"
fi
AC_SUBST([FC_VERSION])
2013-10-31 13:24:22 +08:00
## Strip anything that looks like a flag off of $FC
2010-07-09 10:52:14 +08:00
FC_NOFLAGS=`echo $FC | sed 's/ -.*//'`
if `echo $FC_NOFLAGS | grep ^/ >/dev/null 2>&1`; then
FC_VERSION="$FC"
else
FC_VERSION="$FC";
for x in `echo $PATH | sed -e 's/:/ /g'`; do
if test -x $x/$FC_NOFLAGS; then
FC_VERSION="$x/$FC"
break
fi
done
fi
if test -n "$fc_version_info"; then
FC_VERSION="$FC_VERSION ( $fc_version_info)"
fi
AC_SUBST([CXX_VERSION])
2013-10-31 13:24:22 +08:00
## Strip anything that looks like a flag off of $CXX
2010-07-09 10:52:14 +08:00
CXX_NOFLAGS=`echo $CXX | sed 's/ -.*//'`
if `echo $CXX_NOFLAGS | grep ^/ >/dev/null 2>&1`; then
CXX_VERSION="$CXX"
else
2016-02-29 10:43:00 +08:00
CXX_VERSION="$CXX";
2010-07-09 10:52:14 +08:00
for x in `echo $PATH | sed -e 's/:/ /g'`; do
if test -x $x/$CXX_NOFLAGS; then
CXX_VERSION="$x/$CXX"
break
fi
done
fi
if test -n "$cxx_version_info"; then
CXX_VERSION="$CXX_VERSION ( $cxx_version_info)"
2000-09-15 06:19:24 +08:00
fi
2016-02-29 10:43:00 +08:00
AC_SUBST([JAVA_VERSION])
## Strip anything that looks like a flag off of $JAVA
JAVA_NOFLAGS=`echo $JAVA | sed 's/ -.*//'`
if `echo $JAVA_NOFLAGS | grep ^/ >/dev/null 2>&1`; then
JAVA_VERSION="$JAVA"
else
JAVA_VERSION="$JAVA";
for x in `echo $PATH | sed -e 's/:/ /g'`; do
if test -x $x/$JAVA_NOFLAGS; then
JAVA_VERSION="$x/$JAVA"
break
fi
done
fi
java_version_info=`$JAVA -version 2>&1 |\
grep 'version' | sed -e 's/version "//' | sed -e 's/"//'`
if test -n "$java_version_info"; then
2016-03-22 15:22:52 +08:00
JAVA_VERSION="$JAVA_VERSION ($java_version_info)"
2016-02-29 10:43:00 +08:00
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Where is the root of the source tree. Give an absolute address so
## we can find it no matter which directory of the distribution is our
## current directory. The built-in pwd fails on some systems, but the
## /bin/pwd version works OK.
##
2000-09-15 06:19:24 +08:00
if test -x /bin/pwd; then
2001-09-28 07:05:16 +08:00
pwd=/bin/pwd
[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
else
2001-09-28 07:05:16 +08:00
pwd=pwd
[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
fi
2003-07-29 05:38:04 +08:00
AC_SUBST([ROOT]) ROOT="`$pwd`"
[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
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Some programs shouldn't be built by default (e.g., programs to generate
## data files used by tests, some optional tests).
## Check if they want such programs built anyway.
##
2005-10-15 06:52:13 +08:00
AC_MSG_CHECKING([additional programs should be built])
AC_ARG_ENABLE([build-all],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-build-all],
2005-10-15 06:52:13 +08:00
[Build helper programs that only developers should need [default=no]])],
[BUILD_ALL=$enableval],
[BUILD_ALL=no])
if test "X$BUILD_ALL" = "Xyes"; then
echo "yes"
else
echo "no"
fi
AM_CONDITIONAL([BUILD_ALL_CONDITIONAL], [test "X$BUILD_ALL" = "Xyes"])
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Enable deprecated public API symbols
##
2016-01-28 05:45:23 +08:00
## Enabled unless the build mode is clean.
if test "X-$BUILD_MODE" = "X-clean" ; then
DEPREC_SYMBOLS=no
else
DEPREC_SYMBOLS=yes
fi
2007-07-13 06:01:35 +08:00
AC_SUBST([DEPRECATED_SYMBOLS])
AC_MSG_CHECKING([if deprecated public symbols are available]);
AC_ARG_ENABLE([deprecated-symbols],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-deprecated-symbols],
2016-01-28 05:45:23 +08:00
[Enable deprecated public API symbols.
[default=yes (unless build mode = clean)]
])],
[DEPREC_SYMBOLS=$enableval])
2007-07-13 06:01:35 +08:00
case "X-$DEPREC_SYMBOLS" in
X-yes)
AC_MSG_RESULT([yes])
DEPRECATED_SYMBOLS=yes
;;
X-no|*)
AC_MSG_RESULT([no])
DEPRECATED_SYMBOLS=no
AC_DEFINE([NO_DEPRECATED_SYMBOLS], [1],
[Define if deprecated public API symbols are disabled])
;;
esac
2012-09-12 04:11:44 +08:00
## --------------------------------------------------------------------------
## Which version of the public APIs should the 'base' versioned symbols use?
##
2007-07-13 10:42:17 +08:00
AC_SUBST([DEFAULT_API_VERSION])
AC_MSG_CHECKING([which version of public symbols to use by default])
AC_ARG_WITH([default-api-version],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--with-default-api-version=(v16|v18|v110)],
2007-07-13 10:42:17 +08:00
[Specify default release version of public symbols
[svn-r17582] Description:
Bring changes from file free space branch back to the trunk. *yay!*
Tested on:
FreeBSD/32 6.3 (duty) in debug mode
FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (jam) w/PGI compilers, w/default API=1.8.x,
w/C++ & FORTRAN, w/threadsafe, in debug mode
Linux/64-amd64 2.6 (smirom) w/Intel compilers, w/default API=1.6.x,
w/C++ & FORTRAN, in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in debug mode
Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode
Mac OS X/32 10.5.8 (amazon) in debug mode
Mac OS X/32 10.5.8 (amazon) w/C++ & FORTRAN, w/threadsafe,
in production mode
2009-10-02 10:08:59 +08:00
[default=v110]])],,
2012-09-12 04:11:44 +08:00
[withval=v110])
2007-07-13 10:42:17 +08:00
if test "X$withval" = "Xv16"; then
AC_MSG_RESULT([v16])
DEFAULT_API_VERSION=v16
2008-10-25 03:12:21 +08:00
AC_DEFINE([USE_16_API_DEFAULT], [1],
2007-07-13 10:42:17 +08:00
[Define using v1.6 public API symbols by default])
elif test "X$withval" = "Xv18"; then
AC_MSG_RESULT([v18])
DEFAULT_API_VERSION=v18
2016-02-20 00:21:00 +08:00
AC_DEFINE([USE_18_API_DEFAULT], [1],
[Define using v1.8 public API symbols by default])
[svn-r17582] Description:
Bring changes from file free space branch back to the trunk. *yay!*
Tested on:
FreeBSD/32 6.3 (duty) in debug mode
FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (jam) w/PGI compilers, w/default API=1.8.x,
w/C++ & FORTRAN, w/threadsafe, in debug mode
Linux/64-amd64 2.6 (smirom) w/Intel compilers, w/default API=1.6.x,
w/C++ & FORTRAN, in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in debug mode
Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode
Mac OS X/32 10.5.8 (amazon) in debug mode
Mac OS X/32 10.5.8 (amazon) w/C++ & FORTRAN, w/threadsafe,
in production mode
2009-10-02 10:08:59 +08:00
elif test "X$withval" = "Xv110"; then
AC_MSG_RESULT([v110])
DEFAULT_API_VERSION=v110
2007-07-13 10:42:17 +08:00
else
AC_MSG_ERROR([invalid version of public symbols given])
fi
2012-09-12 04:11:44 +08:00
## It's an error to try to disable deprecated public API symbols while
## choosing an older version of the public API as the default. However,
## if the user insists on doing this via the --enable-unsupported configure
## flag, we'll let them.
2010-11-18 02:07:51 +08:00
if test "X${ALLOW_UNSUPPORTED}" != "Xyes"; then
if test "X${DEFAULT_API_VERSION}" != "Xv110" -a "X${DEPRECATED_SYMBOLS}" = "Xno" ; then
AC_MSG_ERROR([Removing old public API symbols not allowed when using them as default public API symbols. Use --enable-unsupported to override this error.])
fi
2007-07-13 10:42:17 +08:00
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Enable strict file format checks
##
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
AC_SUBST([STRICT_FORMAT_CHECKS])
2013-06-06 02:26:35 +08:00
AC_MSG_CHECKING([whether to perform strict file format checks]);
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
AC_ARG_ENABLE([strict-format-checks],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-strict-format-checks],
2016-01-28 05:45:23 +08:00
[Enable strict file format checks.
[default=yes if debug build, otherwise no]
])],
[STRICT_FORMAT_CHECKS=$enableval])
## Set the default level. This depends on the compiler mode.
if test "X-$STRICT_FORMAT_CHECKS" = X- ; then
if test "X-$BUILD_MODE" = "X-debug" ; then
STRICT_FORMAT_CHECKS=yes
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
else
2016-01-28 05:45:23 +08:00
STRICT_FORMAT_CHECKS=no
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
fi
fi
2016-01-28 05:45:23 +08:00
case "X-$STRICT_FORMAT_CHECKS" in
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
X-yes)
AC_MSG_RESULT([yes])
AC_DEFINE([STRICT_FORMAT_CHECKS], [1],
[Define if strict file format checks are enabled])
;;
2016-01-28 05:45:23 +08:00
X-no)
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
AC_MSG_RESULT([no])
2016-01-28 05:45:23 +08:00
;;
*)
AC_MSG_ERROR([Unrecognized value: $STRICT_FORMAT_CHECKS])
[svn-r14402] Description:
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
2008-01-13 13:37:00 +08:00
;;
esac
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Enable embedded library information
##
2013-06-06 02:26:35 +08:00
AC_MSG_CHECKING([whether to have library information embedded in the executables])
2009-04-21 10:02:46 +08:00
AC_ARG_ENABLE([embedded-libinfo],
2012-09-12 04:11:44 +08:00
[AS_HELP_STRING([--enable-embedded-libinfo],
2016-03-01 22:50:49 +08:00
[Enable embedded library information [default=yes]])],
[enable_embedded_libinfo=$enableval],
[enable_embedded_libinfo=yes])
2009-04-21 10:02:46 +08:00
if test "${enable_embedded_libinfo}" = "yes"; then
AC_MSG_RESULT([yes])
AC_DEFINE([HAVE_EMBEDDED_LIBINFO], [1],
[Define if library information should be embedded in the executables])
else
AC_MSG_RESULT([no])
fi
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Check if pointer alignments are enforced
##
2008-09-19 04:53:30 +08:00
AC_MSG_CHECKING([if alignment restrictions are strictly enforced])
2016-07-19 02:37:17 +08:00
TEST_SRC="`(echo \"#define H5_NO_ALIGNMENT_RESTRICTIONS_TEST 1\"; cat $srcdir/config/cmake/ConversionTests.c)`"
2008-09-19 04:53:30 +08:00
AC_RUN_IFELSE([
2016-07-19 02:37:17 +08:00
AC_LANG_SOURCE([$TEST_SRC])
2008-09-19 04:53:30 +08:00
], [
AC_DEFINE([NO_ALIGNMENT_RESTRICTIONS], [1], [Define if we can violate pointer alignment restrictions])
AC_MSG_RESULT([no])
], [
AC_MSG_RESULT([yes])
], [
AC_MSG_RESULT([unknown, assuming yes])
])
[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
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Restore user's CFLAGS.
2009-10-14 05:55:21 +08:00
CFLAGS="$saved_user_CFLAGS"
2009-10-19 11:05:25 +08:00
FCFLAGS="$saved_user_FCFLAGS"
2009-10-14 05:55:21 +08:00
CXXFLAGS="$saved_user_CXXFLAGS"
2009-10-19 11:05:25 +08:00
CPPFLAGS="$saved_user_CPPFLAGS"
2016-02-29 10:43:00 +08:00
JAVACFLAGS="$saved_user_JAVACFLAGS"
JAVAFLAGS="$saved_user_JAVAFLAGS"
2009-10-19 11:05:25 +08:00
LDFLAGS="$saved_user_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
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Create automake conditionals to tell automake makefiles which directories
## need to be compiled
2005-02-01 11:17:02 +08:00
AM_CONDITIONAL([BUILD_CXX_CONDITIONAL], [test "X$HDF_CXX" = "Xyes"])
AM_CONDITIONAL([BUILD_PARALLEL_CONDITIONAL], [test -n "$TESTPARALLEL"])
AM_CONDITIONAL([BUILD_FORTRAN_CONDITIONAL], [test "X$HDF_FORTRAN" = "Xyes"])
2016-02-29 10:43:00 +08:00
AM_CONDITIONAL([BUILD_JAVA_CONDITIONAL], [test "X$HDF_JAVA" = "Xyes"])
2005-02-01 11:17:02 +08:00
AM_CONDITIONAL([BUILD_HDF5_HL_CONDITIONAL], [test "X$HDF5_HL" = "Xyes"])
2006-06-22 07:15:08 +08:00
2005-02-01 11:17:02 +08:00
2012-09-12 04:11:44 +08:00
## ----------------------------------------------------------------------
## Build the Makefiles.
##
1997-08-16 00:35:53 +08:00
2012-09-12 04:11:44 +08:00
## The directory search list
2003-07-29 05:38:04 +08:00
AC_SUBST([SEARCH]) SEARCH='$(srcdir) $(top_builddir)/src $(top_srcdir)/src'
2000-10-12 01:25:21 +08:00
export SEARCH
1997-08-16 00:35:53 +08:00
2012-09-12 04:11:44 +08:00
## Some cleanup stuff
2009-10-16 02:11:56 +08:00
rm -f conftest conftest.o conftest.c dummy.o *.mod
1997-08-29 00:36:57 +08:00
2012-09-12 04:11:44 +08:00
## Build config.status, touch the stamp files, and build all the Makefiles.
## The order is such that the first `make' does not need to update any
## configuration information. See config/commence.in for the order in which
## things need to be done.
1999-03-23 00:21:49 +08:00
2012-09-12 04:11:44 +08:00
## First the stamp1 file for H5config.h.in
1999-03-23 00:21:49 +08:00
mkdir ./config >/dev/null 2>&1
touch ./config/stamp1
2012-09-12 04:11:44 +08:00
## Then the config.status file (but not makefiles)
1999-03-23 00:21:49 +08:00
saved_no_create=$no_create
1999-03-20 04:09:50 +08:00
no_create=yes
2001-02-23 06:02:01 +08:00
2001-12-18 02:00:24 +08:00
PARALLEL_MAKE=""
2003-07-29 05:38:04 +08:00
FORTRAN_PARALLEL_MAKE=""
2001-04-03 04:33:14 +08:00
if test -n "$TESTPARALLEL"; then
2014-03-22 07:02:24 +08:00
PARALLEL_MAKE="$TESTPARALLEL/Makefile"
2003-07-29 05:38:04 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
FORTRAN_PARALLEL_MAKE=fortran/$TESTPARALLEL/Makefile
fi
2001-04-03 04:33:14 +08:00
fi
2013-03-29 01:17:19 +08:00
LT_OUTPUT
no_create=$saved_no_create
## Then the stamp2 file for H5config.h
touch ./config/stamp2
## Finally the makefiles
test "$no_create" = yes || ${CONFIG_SHELL-/bin/sh} $CONFIG_STATUS || exit 1
## Are we compiling static libraries, shared libraries, or both? This
## is only used for the libhdf5.settings file. We can't just look at
## $enable_static and $enable_shared because if they're yes the ltconfig
## might have decided that one or the other is simply not possible.
## Therefore we have to ask the generated `libtool' shell script
## which 'features' it has enabled.
if (./libtool --features | grep '^enable shared libraries' > /dev/null); then
enable_shared=yes
else
enable_shared=no
fi
if (./libtool --features | grep '^enable static libraries' > /dev/null); then
enable_static=yes
else
enable_static=no
fi
2016-01-28 05:45:23 +08:00
## Expose things for *.in markup
AC_SUBST([STATIC_SHARED])
AC_SUBST([enable_shared])
AC_SUBST([enable_static])
2013-03-29 01:17:19 +08:00
if test "X$enable_static" = "Xyes" && test "X$enable_shared" = "Xyes"; then
STATIC_SHARED="static, shared"
elif test "X$enable_static" = "Xyes"; then
STATIC_SHARED="static"
elif test "X$enable_shared" = "Xyes"; then
STATIC_SHARED="shared"
else
STATIC_SHARED="none"
fi
2017-07-28 00:32:21 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
### libtool does not pass the correct argument linking (-WL,-WL,,) for the NAG Fortran compiler
### on Linux (other OSs have not been tested).
### Therefore, detect if we are using the NAG Fortran compiler, and replace the wl="-Wl," for Fortran to
### wl="-Wl,-WL,," in the libtool file. (HDFFV-10037)
case "`uname`" in
Linux*)
fortran_linux_linker_option="-Wl,"
2017-08-02 04:33:43 +08:00
if test "X$FC_BASENAME" = "Xnagfor"; then
2017-07-28 00:32:21 +08:00
fortran_linux_linker_option="-Wl,-Wl,,"
fi
## Set the correct linker option for use in h5fc.in markup
AC_SUBST([fortran_linux_linker_option])
;;
esac
fi
2013-03-29 01:17:19 +08:00
## ----------------------------------------------------------------------
## Set a macro if shared library is enabled.
##
AM_CONDITIONAL([HAVE_SHARED_CONDITIONAL], [test "X$enable_shared" = "Xyes"])
2001-04-03 04:33:14 +08:00
2002-04-23 07:44:41 +08:00
AC_CONFIG_FILES([src/libhdf5.settings
Makefile
src/Makefile
test/Makefile
2009-09-28 23:44:35 +08:00
test/testcheck_version.sh
2007-08-22 05:08:27 +08:00
test/testerror.sh
2017-01-19 01:10:56 +08:00
test/testflushrefresh.sh
2010-03-18 20:23:04 +08:00
test/H5srcdir_str.h
2009-09-21 13:28:44 +08:00
test/testlibinfo.sh
2010-11-15 12:04:28 +08:00
test/testlinks_env.sh
2017-06-29 14:11:44 +08:00
test/test_filenotclosed.sh
2017-01-27 03:34:12 +08:00
test/testswmr.sh
2013-03-14 03:35:26 +08:00
test/test_plugin.sh
2017-01-27 03:34:12 +08:00
test/test_usecases.sh
test/testvdsswmr.sh
2005-02-01 11:17:02 +08:00
testpar/Makefile
2002-04-23 07:44:41 +08:00
tools/Makefile
tools/lib/Makefile
2016-10-27 23:11:24 +08:00
tools/src/Makefile
tools/src/h5dump/Makefile
tools/src/h5import/Makefile
tools/src/h5diff/Makefile
tools/src/h5jam/Makefile
tools/src/h5repack/Makefile
tools/src/h5ls/Makefile
tools/src/h5copy/Makefile
tools/src/misc/Makefile
tools/src/misc/h5cc
tools/src/h5stat/Makefile
tools/test/Makefile
tools/test/h5dump/Makefile
2017-01-18 07:11:27 +08:00
tools/test/h5dump/h5dump_plugin.sh
2016-10-27 23:11:24 +08:00
tools/test/h5dump/testh5dump.sh
tools/test/h5dump/testh5dumppbits.sh
tools/test/h5dump/testh5dumpvds.sh
tools/test/h5dump/testh5dumpxml.sh
2016-11-07 04:08:19 +08:00
tools/test/h5ls/Makefile
2017-01-18 07:11:27 +08:00
tools/test/h5ls/h5ls_plugin.sh
2016-10-27 23:11:24 +08:00
tools/test/h5ls/testh5ls.sh
tools/test/h5ls/testh5lsvds.sh
tools/test/h5import/Makefile
tools/test/h5import/h5importtestutil.sh
tools/test/h5diff/Makefile
2017-01-18 07:11:27 +08:00
tools/test/h5diff/h5diff_plugin.sh
2016-10-27 23:11:24 +08:00
tools/test/h5diff/testh5diff.sh
tools/test/h5diff/testph5diff.sh
2016-11-03 23:58:43 +08:00
tools/src/h5format_convert/Makefile
tools/test/h5format_convert/Makefile
tools/test/h5format_convert/testh5fc.sh
2016-10-27 23:11:24 +08:00
tools/test/h5jam/Makefile
tools/test/h5jam/testh5jam.sh
tools/test/h5repack/Makefile
tools/test/h5repack/h5repack.sh
tools/test/h5repack/h5repack_plugin.sh
tools/test/h5copy/Makefile
tools/test/h5copy/testh5copy.sh
tools/test/misc/Makefile
2017-01-19 01:10:56 +08:00
tools/test/misc/testh5clear.sh
2016-10-27 23:11:24 +08:00
tools/test/misc/testh5mkgrp.sh
tools/test/misc/testh5repart.sh
tools/test/misc/vds/Makefile
tools/test/h5stat/Makefile
2016-11-07 04:08:19 +08:00
tools/test/h5stat/testh5stat.sh
2016-10-27 23:11:24 +08:00
tools/test/perform/Makefile
2002-04-23 07:44:41 +08:00
examples/Makefile
2010-07-09 10:52:14 +08:00
examples/run-c-ex.sh
2007-04-11 13:17:13 +08:00
examples/testh5cc.sh
2005-02-01 11:17:02 +08:00
c++/Makefile
c++/src/Makefile
c++/src/h5c++
c++/test/Makefile
2010-03-18 20:23:04 +08:00
c++/test/H5srcdir_str.h
2005-02-01 11:17:02 +08:00
c++/examples/Makefile
2010-07-09 10:52:14 +08:00
c++/examples/run-c++-ex.sh
2007-04-11 13:17:13 +08:00
c++/examples/testh5c++.sh
2005-02-01 11:17:02 +08:00
fortran/Makefile
fortran/src/h5fc
fortran/src/Makefile
2015-08-11 22:35:30 +08:00
fortran/src/H5fort_type_defines.h
2005-02-01 11:17:02 +08:00
fortran/test/Makefile
fortran/testpar/Makefile
fortran/examples/Makefile
2010-07-09 10:52:14 +08:00
fortran/examples/run-fortran-ex.sh
2007-04-11 13:17:13 +08:00
fortran/examples/testh5fc.sh
2016-02-29 10:43:00 +08:00
java/Makefile
java/src/Makefile
java/src/jni/Makefile
java/test/Makefile
java/test/junit.sh
java/examples/Makefile
java/examples/intro/Makefile
java/examples/intro/runExample.sh
java/examples/datasets/Makefile
java/examples/datasets/runExample.sh
java/examples/datatypes/Makefile
java/examples/datatypes/runExample.sh
java/examples/groups/Makefile
java/examples/groups/runExample.sh
2005-02-01 11:17:02 +08:00
hl/Makefile
hl/src/Makefile
hl/test/Makefile
2010-03-18 20:23:04 +08:00
hl/test/H5srcdir_str.h
2006-03-04 05:49:10 +08:00
hl/tools/Makefile
hl/tools/gif2h5/Makefile
2012-08-24 00:07:43 +08:00
hl/tools/gif2h5/h52giftest.sh
2017-01-19 01:10:56 +08:00
hl/tools/h5watch/Makefile
2016-12-12 03:25:08 +08:00
hl/tools/h5watch/testh5watch.sh
2005-12-10 04:59:11 +08:00
hl/examples/Makefile
2010-07-09 10:52:14 +08:00
hl/examples/run-hlc-ex.sh
2005-03-29 00:32:20 +08:00
hl/c++/Makefile
hl/c++/src/Makefile
hl/c++/test/Makefile
2005-12-10 04:59:11 +08:00
hl/c++/examples/Makefile
2010-07-09 10:52:14 +08:00
hl/c++/examples/run-hlc++-ex.sh
2005-02-01 11:17:02 +08:00
hl/fortran/Makefile
hl/fortran/src/Makefile
2005-12-10 04:59:11 +08:00
hl/fortran/test/Makefile
2010-07-09 10:52:14 +08:00
hl/fortran/examples/Makefile
hl/fortran/examples/run-hlfortran-ex.sh])
2002-04-23 07:44:41 +08:00
2016-03-18 00:47:21 +08:00
AC_CONFIG_COMMANDS([.classes], [], [$MKDIR_P java/src/.classes;
$MKDIR_P java/test/.classes;
$MKDIR_P java/examples/intro/.classes;
$MKDIR_P java/examples/datasets/.classes;
$MKDIR_P java/examples/datatypes/.classes;
$MKDIR_P java/examples/groups/.classes])
2002-04-23 07:44:41 +08:00
AC_OUTPUT
2008-05-06 02:35:55 +08:00
2016-11-04 00:05:37 +08:00
chmod 755 tools/src/misc/h5cc
2003-07-29 05:38:04 +08:00
if test "X$HDF_CXX" = "Xyes"; then
chmod 755 c++/src/h5c++
fi
2017-07-28 22:05:39 +08:00
if test "X$HDF_FORTRAN" = "Xyes"; then
chmod 755 fortran/src/h5fc
## libtool does not pass the correct argument linker (wl=) for the Intel Fortran compiler
## on OS X, which is needed when building shared libraries on OS X. This script
## replaces the 3rd occurrence, which is for Fortran, of wl="" with wl="-Wl," (HDFFV-2772)
case "`uname`" in
Darwin*)
cat libtool | awk '/wl=\"/{c++;if(c==3){sub("wl=\"\"","wl=\"-Wl,\"");c=0}}1' > libtool.tmp && mv -f libtool.tmp libtool && chmod 755 libtool
;;
esac
### libtool does not pass the correct argument linking (-WL,-WL,,) for the NAG Fortran compiler
### on Linux (other OSs have not been tested).
### Therefore, detect if we are using the NAG Fortran compiler, and replace the wl="-Wl," for Fortran to
### wl="-Wl,-WL,," in the libtool file. (HDFFV-10037)
case "`uname`" in
Linux*)
if (grep -i 'NAG_Fortran' libtool > /dev/null); then
cat libtool | awk '/NAG_Fortran/{flag=1}flag&&/wl=/{$NF="wl=\"-Wl,Wl,,\"";flag=0}1' > libtool.tmp && mv -f libtool.tmp libtool && chmod 755 libtool
fi
;;
esac
fi
2015-04-18 06:24:47 +08:00
## HDF5 configure code created by autotools with gcc 4.9.2 is adding problematic
## linker flags: -l with no library name; -l <libname>, specifically gfortran or m.
## This sed script corrects "-l <libname>" first and then "-l " with no library name.
## If the order is not preserved, all instances of "-l " will be removed.
sed -e '/^postdeps/ s/-l \([a-zA-Z]\)/-l\1/g' -e '/^postdeps/ s/-l //g' -i libtool
2012-09-12 04:11:44 +08:00
## show the configure settings
2008-05-15 13:12:00 +08:00
cat src/libhdf5.settings