A detailed error message is emitted if this combination is attempted.
Builders can use --enable-unsupported to build the combo.
Note that default builds will now need to use --disable-hl with
--enable-threadsafe since the high-level library is built by default.
Part of: HDFFV-8719
Tested on: Local Linux w/ various combinations of configure options.
Various tweaks for autotools thread-safety and Pthreads support.
- Moved the check for pthread_attr_setscope() into the thread-safe
checks section. Documented its necessity and added a cross-compiling
option and helpful comment.
- Moved the high-level library checks up to the same place where
Fortran and C++ are checked. This will make it easier to handle
threadsafe/high-level combinations later.
- Also changed the default of --enable-pthread to 'check', which is
the same as the old 'yes' behavior where we just check the standard
locations. 'yes' and 'no' are still accepted, though 'no' will
currently produce an error since the autotools only support Pthreads.
Fixes: HDFFV-9087
Tested on: h5committest
jam (w/ threadsafe)
Purpose:
Fix HDFFV-9124 - Remove old libtool post-processing
Description:
This revision removes some post-processing of the generated libtool
script, which was added back in 2003 (see svn revisions 6285 and 6293)
to address a deficiency in which the script failed to set the '$wl'
variable for icc and pgcc compilers. Libtool has since fixed the issue,
and the post-processing we've been running has essentially been a no-op
for years, so it's safe for us to remove the post-processing snippet.
Tested:
Jam using pgcc and icc compilers.
Since off_t is exposed by the C API, the large file definitions MUST
be exposed so that client code matches the library.
These definitions have been switched back to AM_CPPFLAGS, which is
exported to h5cc, etc. The POSIX and GNU definitions changes from
r26347 have been left as using H5_CPPFLAGS, which is not sent to
h5cc as we don't want to inflict our needs on external users.
Fixes: HDFFV-9152
Tested on: h5committest
which is where the rest of the #defines reside.
The key difference is that AM_CPPFLAGS is exported to h5cc. These #defines
are not necessary to consume the HDF5 API and it's bad form to inflict
our build configuration on users. In particular, the GNU/POSIX defines
could easily conflict with a user's.
Fixes: HDFFV-9152
Tested on: h5committest
branch.
Removed the configure option that allows selective disabling of individual
internal filters (fletcher32, shuffle, etc.).
This feature mucked up the code with a lot of #ifdefs, saved very little space,
and was not scalable to a general scheme for library size reduction. We've
decided to remove the feature while we investigate a more general scheme for
decreasing the library size.
Part of: HDFFV-9086
Tested on: h5committest
Fix HDFFV-9124 - Remove old libtool post-processing
Description:
This revision removes some post-processing of the generated libtool
script, which was added back in 2003 (see svn revisions 6285 and 6293)
to address a deficiency in which the script failed to set the '$wl'
variable for icc and pgcc compilers. Libtool has since fixed the issue,
and the post-processing we've been running has essentially been a no-op
for years, so it's safe for us to remove the post-processing snippet.
Tested:
Jam using pgcc and icc compilers.
Cleans up time functions in the autotools input files. Removed deprecated
gettimeofday() time zone code and configure processing. Also removed
some unused time function configure checks and defines.
Fixes: HDFFV-9083 and HDFFV-9085
Tested on: 32-bit linux, serial and parallel (jam)
OS X (kite)
Solaris (emu)
- 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.
Removes the --with-default-vfd option from configure. This was basically
useless and only allowed selecting the stdio VFD. Since this is a demo
VFD and not really a production VFD, we decided to retire this option.
Fixes: HDFFV-9081
Tested on: h5committest
NOTE: platypus cmake fails, but this is not a new error.
by default (unlike the trunk and 1.8 branches, where it's disabled
by default).
Users can build with --disable-maintainer-mode to remove autotools
build dependencies.
Part of: HDFFV-9122
Tested on: 64-bit linux VM (configure and autogen only)
Remove LDOUBLE_TO_INTEGER_WORKS macro/define from configure/library/tests,
since it was added to support non-standard behavior on SGI IRIX & HP-UX, which
we don't support any longer.
Tested on:
Mac OSX/64 10.10.2 (amazon) w/serial & parallel
(h5committest not required on this branch)
Remove the LDOUBLE_TO_INTEGER_ACCURATE macro, since it was added to work
around non-standard behavior on SGI IRIX, which we are no longer supporting.
Tested on:
Mac OSX/64 10.10.2 (amazon) w/serial
(h5committest not required on this branch)
unsupported Code Warrior compiler. Also removes the H5_NO_SHARED_WRITING
symbol from the pubconf file.
Fixes: HDFFV-9080
Tested on: jam only, after bin/reconfigure
(all platforms should see no source changes)
Adds a comment to configure.ac indicating that Cygwin still has
problems with srcdir and time.
Fixes: HDFFV-9082
Tested on: jam (comment only change) w/ bin/reconfigure
- Remove Infering parallel compilers (C and Fortran) from configure.ac
- Remove restriction to build shared with parallel
- Cleanup parallel sections in configure.ac
- remove large file support checks
- MPE fixes.
tested with h5committest.
Long time ago, the tr command in some platform does not work properly and this test was added
to detect broken tr and abort the configure process.
We are not aware of such broken tr command in current systems and decided to retire this test.
The setup of ${TR} is still needed as it is used to process DEBUG_PKG.
Tested: h5committested plus using "./configure --enable-debug=all" in jam.
Long time ago, the tr command in some platform does not work properly and this test was added
to detect broken tr and abort the configure process.
We are not aware of such broken tr command in current systems and decided to retire this test.
The setup of ${TR} is still needed as it is used to process DEBUG_PKG.
Tested: in jam using "./configure" and "./configure --enable-debug=all".
Removed restiction of disabling shared libraries on the MAC, H5_FORTRAN_SHARED was replaced with HAVE_SHARED_CONDITIONAL since H5_FORTRAN_SHARED was removed.
tested: jam
- Results of O_DIRECT and posix_memalign() checks are now
output so users can more easily diagnose problems.
- Configure now fails if --enable-direct-vfd was requested
but either O_DIRECT or posix_memalign() are not
present.
Part of HDFFV-7566
Tested on: jam (configure only)
to build and run a program using it, which is problematic (depends on
file system, issues with cross-compiling).
Part of HDFFV-9057
Tested on: jam (configure only)
Fortran and C++ are checked. This will make it easier to
handle threadsafe/high-level combinations later.
Also changed the default of --enable-pthread to 'check' and
removed yes/no behavior. If you ask for thread-safety, you
can't disable Pthreads...
Part of HDFFV-8719
Tested on: jam (configure only)
section. Documented its necessity and added a cross-compiling option
and helpful comment.
Also removed a check for BSDgettimeofday from configure.ac, which
was for Irix 5.3 support.
Part of HDFFV-9087
Tested on: jam with threadsafe
405-408::fortran vars should be scoped
Scoped:
HAVE_SIZEOF
HAVE_C_SIZEOF
HAVE_STORAGE_SIZE
FORTRAN_DEFAULT_REALisDBLE
to where the tests are (in m4/aclocal_fc.m4)
Tested: jam (gnu)
4159:: Check if Fortran's default real is double precision. If it is and HL is being built then configure should fail due to bug HDFFV-889.
Fix:
This check should be located where HL is check for, and it is. Updated the comment to elimenate confusion.
