summaryrefslogtreecommitdiffstats
path: root/src/H5config.h.in
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r21101] HDFFV-7639Mike McGreevy2011-07-141-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Purpose: Remove H5_MPI_SPECIAL_COLLECTIVE_IO_WORKS and H5_MPI_COMPLEX_DERIVED_DATATYPE_WORKS #defines from source. Description: Two advanced parallel functionalities, special collective IO and complex derived datatypes, are not supported by older implementations of mpi, and thus our code limits the use of these features with #ifdefs and has checks in configure to set them (or not). Unfortunately, configure can't actually run a parallel check to see if these features are working (nor not) so it resorts to looking in the config files where they are explicity enabled or disabled based on versions of mpi, sytems being built on, or for no documented reason at all (i.e. just set to on or off as some 'default'). Overriding these settings is easy if need be, provided it is known that it needs to be done to get improved performance, and oftentimes it is not. Most new MPI implementations successfully handle the functionality requested when these #defines are set, and many of the "turn these features off" cases in the config files are for old (> 5 years) versions of MPI and retired systems (such as NCSA's tungsten). Therefore, the decision has been made to remove the support for these old versions of MPI and systems that cannot handle these behaviors. The #ifdefs and supporting setup in the config/ files and configure script has been removed, and the code executed when these options were not set removed from the source. In passing, this commit also cleans up some whitespace issues in both t_mpi.c and H5Dmpio.c. Furthermore, in t_mpi.c, the special collective IO test was not getting regularly run due to it being written to work only with four processes (we regularly test with six, previously with three), and thus it failed when actually run due to an out of bounds data buffer assignment. It has been modified to run at any number of processes greater than four, and the memory problem has been fixed so the test passes. Tested: jam, h5committest, ember
* [svn-r20892] Purpose:Dana Robinson2011-05-231-0/+3
| | | | | | | | | | | Adds a check for the mach_time header file. Description: The mach time header file is needed for the monotonic timer / log VFD work. No code in the trunk depends on this file at this time. Tested on: jam(linux32-LE) tejeda(darwin32 LE) local darwin64 (snow leopard)
* [svn-r20502] Purpose:Mike McGreevy2011-04-141-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | Add "silent make" mode configure option. Description: Automake 1.11 has a new option available that allows for a silent make mode. This functionality needs to be explicitly enabled in configure.in via the use of the automake macro AM_SILENT_RULES, which is what this commit is adding. This introduces a new configure option: --{en|dis}able-silent-rules This option is on by default, and simplies compile and link line outputs when building the library. Disabling this option will print full "verbose" output (i.e., full compile and linking lines for each target). Tested: This was tested on jam & h5committested
* [svn-r20476] Removed all references to memory.hDana Robinson2011-04-111-3/+0
|
* [svn-r19696] Bug 2008 - IBM Power6 Linux uses special conversion algorithms ↵Raymond Lu2010-10-281-0/+8
| | | | | | | | | | | to convert some values from long double to (unsigned) long and from (unsigned) long to long double. I added tests in configure.in to detect these algorithms. Before I can figure out them, I disable the tests in dt_arith.c. There are property changes to tools/misc, config, and Makefile.am when I brought the fix from 1.8. Tested on jam, heiwa, amani, IBM Power6 Linux machine in Holland (huygens.sara.nl).
* [svn-r19205] Bug 1917: post cleanup.Albert Cheng2010-08-091-3/+0
| | | | | | | | | | fseek64 was used to support large file access for the STDIO driver back in version 1.2.2 in year 2000. Some how it was not included in version 1.4.0. Now, fseeko64 is used to support large file. There is no more need for fseek64 which is not a standard call. Removed its presence from configure and related files. Tested: jam for configure only.
* [svn-r19160] Added the tests for fseeko64 and ftello64 which will be used by ↵Albert Cheng2010-07-301-0/+6
| | | | | | | | | the STDIO VFD if they are available. Tested: jam only since it was tests for two new functions that are not used by the code yet.
* [svn-r18709] Purpose:Mike McGreevy2010-05-051-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | Improve configure's large-file support control. Description: Modified configure to now attempt to add defines necessary for supporting largefiles on all systems, instead of solely on linux. This is in response to user requests to enable largefile support on Solaris by default, as well as to give extra control on AIX (instead of just jamming the necessary flag into the config files). The old --enable-linux-lfs flag has been removed in favor of the --enable-largefile flag (enabled by default), which can be used on all platforms. On systems where large files cannot be supported in this manner, configure will report as such. Tested: h5committest AIX (NCSA's blue_print machine) duty, liberty, and linew.
* [svn-r18659] Bug: 1764Albert Cheng2010-04-281-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Description: longjmp do not necessary restore signal that is blocked during the signal handling. This caused the Alignment test to fail quietly, resulting in wrong alignment information which will cause failures later. Solution: One can use sigsetjmp/siglongjmp to restore signal handling but not all systems such as Cray XT or VMS supports sigsetjmp. Backup solution is to use sigprocmask to reset the signal. Again, some systems may not support it either. Added code to try the first and then the second solution. Also added tests to verify if the signal_handler routines are working properly. Finally, added code to print results of the verification (in form of comments) to H5Tinit.c for inspection in case of failure. (Note that many platforms do not have alignment limits at all and ALIGNMNET code never raise the SIGBUS or SIGSEGV errors. In those cases, it does not matter whether the signal handlers work or not. Again, this can be deduced from the results comments near the end of the H5Tinit.c. If the sum of signal handlers called equals the total of verify, it means ALIGNMENT does not raise any signals.) For configure.in and configure: Added the test for setjmp, sigsetjmp, sigprocmask which are used by the H5detec.c. Tested: htcommittested, jam(serial).
* [svn-r18634] Description:Quincey Koziol2010-04-271-0/+6
| | | | | | | | | | | | | | | | | | | | | Clean up compiler warnings. 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 (amani) 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.6.3 (amazon) in debug mode Mac OS X/32 10.6.3 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r18579] Purpose:Mike McGreevy2010-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Autotool Upgrade / Libtool Bug Fix Description: Updated autotools referenced in bin/reconfigure as follows: Autoconf 2.64 --> Autoconf 2.65 Automake 1.11 --> Automake 1.11.1 Libtool 2.2.6a --> Libtool 2.2.6b-mcg The referenced libtool version is a custom version of 2.2.6b. It has been tweaked to fix a bug in libtool that occurs when using PGI 10.0 compilers. A check incorrectly categorizes the C++ compiler as version 1.0 instead of 10.0, and the link line is subsequently set up incorrectly and fails to compile. A patch has been made available and will be included in the next release of libtool, but in the meantime I've applied the patch to a custom installation as indicated above. This bin/reconfigure now references the custom installation, and the resulting configure script will correctly categorize the PGI 10.0 C++ compiler. Ran bin/reconfigure to regenerate configure and makefiles. Tested: jam and amani with PGI 10.0 compilers. h5committest
* [svn-r17939] Description:Quincey Koziol2009-12-011-0/+3
| | | | | | | | | | | | | | | | | | | | | | | Handle external links from symlinked files by adding another check to look for "child" files for links from the actual location of the "parent" file, instead of from the location of the symlink. 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.6.2 (amazon) in debug mode Mac OS X/32 10.6.2 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17924] Description:Quincey Koziol2009-11-231-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add detection for POSIX lstat() routine to configure script (mostly for non-UNIX/Linux machines) and add macro wrapper for it. Alphabetatize the system/library calls we test for, to make them easier to read. Removed the sigaction() detection & macro wrappers, since it's not used by the distribution currently. 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.6.2 (amazon) in debug mode Mac OS X/32 10.6.2 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17392] I added a detection for the correctness of converting from ↵Raymond Lu2009-08-201-0/+4
| | | | | | | | | | unsigned long to float in the configure.in. The Pathscale compiler on Sandia's Linux machine misinterprets the values of unsigned long as negative during the conversion to float, when the first bit of unsigned long is on. Tested on jam. Need to test it on Sandia's machine.
* [svn-r17345] Purpose:Mike McGreevy2009-08-121-4/+18
| | | | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Installed new autotools and used them to reconfigure HDF5. - Automake upgraded to 1.11 - Autoconf upgraded to 2.64 - bin/reconfigure script edited to use new versions (on jam), and run to generate new configure script and Makefile.in's. - configure.in script edited to add "_cv_" to all AC_CACHE_VAL strings (in order to comply with new autoconf standard). Tested: Tested on machines jam, smirom, liberty, linew. Tested w/ features c++, fortran, parallel. Tested w/ compilers gcc, pgcc, icc. Further testing via Daily Tests should catch any other outliers. Upon passing DT's, I'll propogate the new tools into 1.8, hdf4, et cetera.
* [svn-r16847] Description:Quincey Koziol2009-04-231-0/+3
| | | | | | | | | | | | | Bring r16846 from revise_chunks branch back to trunk: Fix broken (for how long?) H5_ASSIGN_OVERFLOW macro to actually detect overflows during assignments, along with several errors it [now] detected. Cleaned up a fix minor warnings and/or pieces of code also. Tested on: FreeBSD/32 6.3 (duty) in debug mode (h5committest not needed - multi-platform test performed on branch)
* [svn-r16814] New feature(Bug 230):Albert Cheng2009-04-211-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | Embed the content of libhdf5.settings into the hdf5 executables so that an "orphaned" executables can display (via the Unix strings command, for example) the library settings used to build the executables. This is a prototype implementation. Much improvement is needed. configure.in: Added the --disable-embedded-libinfo option to disable this feature. configure: src/H5config.h.in: Generated by autotools like automake. src/H5detect.c: Implement insert_libhdf5_settings() to insert the contents of libhdf5.settings into the library as an extern string variable so that it is included in all HDF5 executable. Much improvement is needed. fortran/src/Makefile.in: Auto-generated by bin/reconfigure. (i.e., I did make any changes to cause its direct regeneration). Tested: Jam serial, using default and --disable-embedded-libinfo, configure options.
* [svn-r16306] Description:Quincey Koziol2009-01-141-2/+6
| | | | | | | | | | | | | | Bring r16305 back from revise_chunks branch: Add detection of C99 "designated initializers" to configure script and use new H5_HAVE_C99_DESIGNATED_INITIALIZER macro to conditionally compile default layout variables in src/H5Pdcpl.c Also, minor code cleanups, etc. Tested on: FreeBSD/32 6.3 (duty) in debug mode (Other platforms tested on branch)
* [svn-r15943] Changed the library's macros H5_USE_16_API to ↵Raymond Lu2008-10-241-1/+1
| | | | | | | | | H5_USE_16_API_DEFAULT avoid possible conflict wi th user's definition of H5_USE_16_API. The H5_USE_16_API_DEFAULT is defined through configure with the flag --with-default-api-version=v16. Tested with h5committest.
* [svn-r15825] Description:Quincey Koziol2008-10-091-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | Fix various problems with a the core & sec2 VFDs. Improve the h5_get_file_size() routine to handle files created with VFDs that use multiple files. Tested on: Mac OS X/32 10.5.5 (amazon) in debug mode Mac OS X/32 10.5.5 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode FreeBSD/32 6.3 (duty) in debug mode FreeBSD/64 6.3 (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/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 production mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode
* [svn-r15656] Purpose: fix bug 1286Neil Fortner2008-09-181-0/+3
| | | | | | Description: Added configure test to see if pointer alignment restrictions are enforced (as in dereferencing an unaligned pointer causes an error). Added code in H5Tvlen.c to avoid dereferencing unaligned pointers, conditionally compiled based on the configure test. Added test case in dtypes.c which would previously cause such machines to fail. Tested: kagiso, smirom, linew (h5committest); linew64
* [svn-r15639] Purpose: Check for __func__ keyword during configureScott Wegner2008-09-171-0/+3
| | | | | | | | | | Description: In some of the new H5EA* code, many new C99 features are being used. Most of them are portable to all compilers, but the __func__ keyword in particular isn't supported in Visual Studio on Windows. Instead, Windows defines the __FUNCTION__ keyword, which can be used as a direct substitute. We now check for the __func__ keyword during configure and define the feature flag H5_HAVE_C99_FUNC. There was previously a check for __FUNCTION__, and the feature flags H5_HAVE_FUNCTION. In H5EApkg.h, we check for the presents of each of these in order to see which to use. If neither are avaiable, fail. Tested: h5committest (kagiso, smirom, linew)
* [svn-r15007] Purpose: configure cleanupMike McGreevy2008-05-151-3/+0
| | | | | | | Description: cleaning up configure related to removal of --disable-hsizet flag, which we no longer support. Tested: kagiso
* [svn-r14933] Purpose: Updating HDF5 to use automake 1.10.1 and libtool 2.2.2Mike McGreevy2008-05-051-0/+4
| | | | | | | | | | | | | | | | | | Description: Applying update to autotools that was applied to 1.8 a couple of weeks ago to the trunk. Updated bin/reconfigure script to reflect the new versions of libtool and automake in the /home1/packages/ directory. Rearranged configure.in script. When using libtool 2.2.2, the libtool script doesn't generate until later in the configuration process, so I had to move a test that parsed through the libtool script to a point after where it was actually being generated. Ran libtoolize on the project, and ran bin/reconfigure to regenerate configure and Makefile.in's throughout. Tested: kagiso, smirom, linew (h5committest)
* [svn-r14903] Undoing change committed in r14902.Scot Breitenfeld2008-04-301-0/+3
|
* [svn-r14902] Merged fortran_1_8 branch changes r14505:14901 into the trunk. ↵Scot Breitenfeld2008-04-301-3/+0
| | | | New fortran wrappers added.
* [svn-r14789] Add handling for external link:Vailin Choi2008-04-021-0/+3
| | | | | | | 1. src/H5F.c, src/H5system.c: formulate path for mainfile 2. src/H5Lexternal.c: add search for target file 3. configure.in: add H5_HAVE_WINDOW_PATH 4. test/links.c: add tests for external link
* [svn-r14402] Description:Quincey Koziol2008-01-131-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* [svn-r14270] Description:Albert Cheng2007-11-201-15/+0
| | | | | | | | | | Removed the stream-vfd from the basic library code. (The stream-vfd source files are not removed yet but the MANIFEST has been updated to NOT release those stream-vfd source files.) Platforms tested: Kagiso and smirom. Then test the release tar ball in kagiso.
* [svn-r14211] Description:Quincey Koziol2007-10-181-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | Remove --enable-hdfv1_6 configure flag, now that all dependencies on it have been removed and new --with-default-api-version=[v16|v18] and --disable-deprecated-symbols flags have taken its place. Update types in bin/trace so that bin/reconfigure runs cleanly. Run bin/reconfigure to regenerate configure script, along with other associated files, etc. 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
* [svn-r14047] Purpose: Adding H5_HAVE_SIGLONGJMP macro to configure.Mike McGreevy2007-08-071-0/+3
| | | | | | | Description: Configure will now detect the presence of the 'siglongjmp' function. If present, the macro H5_HAVE_SIGLONGJMP will be defined in src/H5pubconf.h. Tested: kagiso, smirom, linew
* [svn-r13972] Description:Quincey Koziol2007-07-131-0/+3
| | | | | | | | | Add --with-default-api-version configure flag. Tested on: Mac OS X/32 10.4.10 (amazon) FreeBSD/32 6.2 (duty) Linux/32 2.6 (kagiso)
* [svn-r13971] Description:Quincey Koziol2007-07-121-0/+3
| | | | | | | | | | | | | | Add --enable-deprecated-symbols configure option, to allow users to remove deprecated public API symbols at configure time. Add bin/make_vers script to bin/reconfigure actions. Run bin/reconfigure to regenerate autotool components. Tested on: Mac OS X/32 10.4.10 (amazon) FreeBSD/32 6.2 (duty) Linux/32 2.6 (kagiso)
* [svn-r13928] Purpose: 1) Moving H5_CXX_HAVE_OFFSETOF macro to ↵Mike McGreevy2007-06-291-3/+3
| | | | | | | | | | src/H5pubconf.h file. 2) Removing configuration of c++/src/H5cxx_pubconf.h file. Reasoning: the additional pubconf file caused compilation complications, this is cleaner. Tested: kagiso, smirom
* [svn-r13925] Purpose: intermediate checkin for offsetof fix for PGI compiler.Mike McGreevy2007-06-281-1/+1
| | | | | | | | | | Description: added new configuration to generate a pubconf file in the c++/src directory, H5cxx_pubconf.h. When C++ compiler recognizes 'offsetof', the macro H5_CXX_HAVE_OFFSETOF is defined in the new pubconf file. tested: kagiso, smirom
* [svn-r13865] Purpose: Adding a new macro, H5_HAVE_OFFSETOF.Mike McGreevy2007-06-141-0/+3
| | | | | | | | Description: When the compiler has the __offsetof__ extension, the H5_HAVE_OFFSETOF macro will be defined. When the compiler does not have the extension, the macro will remain undefined. Tested: kagiso
* [svn-r13849] Purpose: adding a --with-default-vfd= flag to configuration.Mike McGreevy2007-06-111-0/+3
| | | | | | | | Description: this flag will define the macro H5_DEFAULT_VFD in src/pubconf.h and set it to be either H5FD_SEC2 or H5FD_STDIO, depending on the value set with the configuration flag (either sec2 or stdio). Tested: kagiso, smirom, linew
* [svn-r13829] Some systems (only SGI Altix ProPack 4 discovered so far) ↵Raymond Lu2007-06-021-0/+3
| | | | | | | | | | | | doesn't return correct file size from MPI_File_get_size. Bypass this problem by replacing it with stat. Add an option --disable-mpi-size in configure to indicate this function doesn't work properly. Add a test in testpar/t_mpi.c, too. If it returns wrong file size, print out a warning. Tested on kagiso (parallel) because already tested the same change to v1.6 on several platforms (kagiso, cobalt, copper, and sol).
* [svn-r13815] Description:Quincey Koziol2007-05-291-0/+9
| | | | Regenerate configuration files after latest checkin
* [svn-r13588] A support of files bigger than 2GB for STDIO driver. Configure ↵Raymond Lu2007-04-041-0/+6
| | | | | | | | will check if fseeko is available. Using it instead of fseek can support big files because the offset is of type off_t not long int. Also added the test for STDIO in big.c.
* [svn-r13432] Changed the detection of alignment requirement for Direct I/O ↵Raymond Lu2007-02-281-3/+0
| | | | | | from configuration to run-time detection in H5FD_direct_open in H5FDdirect.c.
* [svn-r12882] Changed bin/reconfigure to work on kagiso as well as on AFS ↵James Laird2006-11-081-38/+42
| | | | | | | | Linux machines. Updated to the latest versions of autotools. Tested on kagiso, heping, and juniper. Let me know if you have any problems.
* [svn-r12870] Add a new macro H5_HAVE_DIRECT_ALIGN in configure.in. Some ↵Raymond Lu2006-11-061-0/+3
| | | | | | | systems like copper and sleipnir doesn't require alignment for Direct I/O. If this's true, write or read data just like sec2 does.
* [svn-r12739] Added Direct I/O driver to VFD. It's only supported by SGI ↵Raymond Lu2006-10-101-0/+3
| | | | | | | | | | Altix (cobalt). There's a configure option --enable-direct-vfd/--disable-direct-vfd to enable/disable Direct I/O support. The default is enabled. There's a small test in test/vfd.c. Another way to test it is to set environment variable HDF5_DRIVER to "direct" and run "make check" in the test/ directory. There'll be some further improvement in the following checkin including allowing user to provide memory boundary value, file block size, and copying buffer size.
* [svn-r12715] Incorporated a user-submitted patch to better detect the 'tr' ↵James Laird2006-10-031-0/+3
| | | | | | | | | | | | utility and quote its arguments. Also checks for the 'socket' library on Solaris. If this patch passes the Daily Tests and makes the user happy, I'll port it back to the 1.6 branch. Tested on mir and sol.
* [svn-r12700] Alert:Quincey Koziol2006-10-021-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | File format is not stable, don't keep files produced! Description: First stage of checkins modifying the format of groups to support creation order. Implement "dense" storage for links in groups. Try to clarify some of the symbols for the H5L API. Add the H5Pset_latest_format() flag for FAPLs, to choose to use the newest file format options (including "dense" link storage in groups) Add the H5Pset_track_creation_order() flag for GCPLs, to enable creation order tracking in groups (although no index on creation order yet). Remove --enable-group-revision configure flag, as file format issues are now handled in a backwardly/forwardly compatible way. Clean up lots of compiler warnings and other minor formatting issues. Tested on: FreeBSD/32 4.11 (sleipnir) w/threadsafe Linux/32 2.4 (heping) w/FORTRAN & C++ Linux/64 2.4 (mir) w/enable-v1.6 compa Mac OSX/32 10.4.8 (amazon) AIX 5.3 (copper) w/parallel & FORTRAN
* [svn-r12669] Description:Quincey Koziol2006-09-151-0/+3
| | | | | | | | Use a slightly less efficient method of computing the log2() on SGI IRIX64, in order to avoid a compiler bug when optimizations are turned on. Tested on: SGI IRIX64 6.5 (atlantia)
* [svn-r12462] Committed a variety of metadata cache related changes:John Mainzer2006-07-131-0/+3
| | | | | | | | | | | | | | | | | | | | | | 1) Added trace file support to the metadata cache. This allows capture of all metadata cache calls in trace files for purposes of optimization and debuging. 2) Added an expunge entry function. This allows an entry to be deleteded from the cache without writing it to disk even if it is dirty. 3) Added a function call to resize pinned entries. 4) Added code to deal with entries that are dirty on load. This is needed in support of a bug fix which can alter object headers on load to repair files. 5) Added progress reporting code to the "MDC API smoke check" test in cache_api.c. To enable the progress reporting, set report_progress to TRUE in mdc_api_call_smoke_check(). Tested with h5committest, and a parallel test on phoenix (dual athelon linux box).
* [svn-r12435] Purpose: Bug fixRaymond Lu2006-06-231-0/+4
| | | | | | | | | | | | Description: Mac OS 10.4 on PowerPC chip has some errors to convert (unsigned) long long to long double. When the bit sequences are 0x003ff..., 0x007fff..., 0x00ffff..., 0x01ffff..., 0x7fffff..., the converted values are twice as big as they should be. Solution: Detect the error in configure and disable the compiler conversion and test case. Platforms tested: h5committest, Mac OS 10.4, and fuss.
* [svn-r12425] Purpose: Bug fixRaymond Lu2006-06-201-0/+4
| | | | | | | | | | | | | | | Description: Data conversion from long double to (unsigned) long long returns some incorrect values on Mac OS 10.4 and SGI IRIX64 6.5. The conversions start to go wrong when the long double is 20041683600089727.779961 (0x4351ccf385ebc8a0bfcc2a...). If adjusting the values higher by assigning 0x...c8a0cf... or 0x...c8a0df..., the converted values go wild. Solution: Detect this error in configure.in and disable compiler conversions from long double to (unsigned) long long for Mac OS 10.4 and IRIX64 6.5. Platforms tested: h5committest, Mac OS 10.4, and IRIX64 6.5.