diff options
author | Mike McGreevy <mamcgree@hdfgroup.org> | 2010-11-17 18:07:51 (GMT) |
---|---|---|
committer | Mike McGreevy <mamcgree@hdfgroup.org> | 2010-11-17 18:07:51 (GMT) |
commit | 8897a3dcbdcb5569b0a0e3d15cef452beb683e98 (patch) | |
tree | fb69979e23b6ac841535c98613218a4218275660 /release_docs | |
parent | 30be8ee01c503bfd2f92c27ebcc0c3bef8b6e0a5 (diff) | |
download | hdf5-8897a3dcbdcb5569b0a0e3d15cef452beb683e98.zip hdf5-8897a3dcbdcb5569b0a0e3d15cef452beb683e98.tar.gz hdf5-8897a3dcbdcb5569b0a0e3d15cef452beb683e98.tar.bz2 |
[svn-r19808] Purpose:
Add "--enable-unsupported" configure flag.
Description
The "--enable-unsupported" configure flag allows a user to
prevent configure from failing due to the use of incompatible
options, such as c++ with parallel.
Specifying --enable-unsupported will bypass all of configure's
checks for incompatible and unsupported combinations of flags.
There are no guarantees that the library will be configured
in any sort of working condition, but that's the risk of
using the --enable-unsupported flag.
I've changed all default error messages related to unsupported
option combinations to indicate that using --enable-unsupported
will allow configure to complete without error.
Tested:
by hand on jam, tested all unsupported configure option
combinations with and without the new flag, making sure
the flag allows configure to finish without error.
(h5committest wouldn't do any good here; it won't test
the new option, and since we're enabling unsupported
combinations, failures are likely to occur in build or
tests with --enable-unsupported turned on anyways.
That's why they're unsupported!)
Diffstat (limited to 'release_docs')
-rw-r--r-- | release_docs/RELEASE.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt index 1d17c4e..2a60b70 100644 --- a/release_docs/RELEASE.txt +++ b/release_docs/RELEASE.txt @@ -39,6 +39,12 @@ New Features Configuration: ------------- + - Added a new configure option, "--enable-unsupported", which can + be used to stop configure from preventing the use of unsupported + configure option combinations, such as c++ in parallel or parallel + HDF5 with threadsafe. Use at your own risk, as it may result in a + library that won't compile or run as expected! + (MAM - 2010/11/17 - Bug 2061) - PHDF5 changed to use "mpiexec", instead of mpirun, as the default MPI applications startup command as defined in the MPI-2 definition, section 4.1. (AKC - 2010/6/11 - Bug 1921) |