summaryrefslogtreecommitdiffstats
path: root/test/Makefile.in
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r21122] Description:Quincey Koziol2011-07-181-1/+1
| | | | | | | | | | | | | Bring r21120 from trunk to 1.8 branch: Check in ugly version of fix for Jira #7638. I'm going to leave the issue open in Jira and when the library has been refactored to use shared file pointers (instead of top file pointers) for file operations, I'll uncomment the check in src/H5Oshared.c Tested on: Mac OS X/32 10.6.8 (amazon) w/debug (too small for h5committest)
* [svn-r21044] Purpose:Mike McGreevy2011-06-281-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix HDFFV-7592 "Remove PACKEDBITS option from autotools files" Description: The code for h5dump's packed bits feature was conditionally compiled in via this option during its 'beta' release in 1.8.5. Now that the feature is fully supported, h5dump has since been changed to always compile the packed bits code (having removed the #ifdef H5_HAVE_H5DUMP_PACKED_BITS checks), so this option in configure is no longer needed. This commit removes the --enable-h5dump-packed-bits configure option, including the help summary from './configure --help' and the libhdf5.settings output summary, the PACKED_BITS Makefile variable, and the definition of H5_HAVE_H5DUMP_PACKED_BITS define in appropriate pubconf header files (which has already been removed from use in source code as of r20722). Note that this option was never added to the trunk, thus this commit only need occur on the 1.8 branch. Tested: - Configure output, help, & summary verified on jam - h5committested
* [svn-r21024] Bug fix for Issue 2598 - In v1.6 library, there was EOA for the ↵Raymond Lu2011-06-231-1/+2
| | | | | | | | | | | | | whole MULTI file saved in the super block. We took it out in v1.8 library because it's meaningless for the MULTI file. v1.8 library saves the EOA for the metadata file, instead. But this caused some backward compatibility problem. v1.8 library couldn't open the file created with v1.6 library. I fixed the problem by checking the EOA value to detect the file created with v1.6 library. Tested on jam, koala, and linew.
* [svn-r20525] Description:Mike McGreevy2011-04-151-79/+104
| | | | | | | | Merge revisions 20475, 20502, and 20504 from trunk to 1.8 branch. Tested: Tested on jam, fred, bangan (CYGWIN), and h5committested.
* [svn-r20489] Bug 1386 - allow dimension size to be zero even though it isn't ↵Raymond Lu2011-04-131-2/+2
| | | | | | | | | | | | | | | | unlimited. I brought the changes from the trunk as below: 1. I added test cases for contiguous, compact, and chunked, and external storage datasets, and also attribute. The test includes dataspace selections. 2. I added a test case of extending dataset of zero dimension size and shrinking back to zero dimension size. 3. I updated the Makefile to include the new data file to be cleaned up. 4. The dataspace code has another bug - when the maximal dimension isn't passed in for H5Sset_extent_simple, it is supposed to be same as the dimension. The current library sets NULL to it. I corrected it and added a test case to it. 5. I corrected the tests of Fortran and C++ for the problem in point 3. Tested on jam, heiwa, and amani.
* [svn-r20114] Merge r20112 (open_file_pool) into 1_8 branch.Neil Fortner2011-02-171-18/+28
| | | | Tested: jam (open_file_pool branch tested with h5committest)
* [svn-r19862] Updated libtool to version 2.4, autoconf to version 2.68, and ↵Larry Knox2010-12-011-0/+3
| | | | | | m4 to version 1.4.15. Tested with h5committest on amani, jam and heiwa.
* [svn-r19824] 1. Made fixes as in rev #19813 in trunk:Vailin Choi2010-11-181-10/+21
| | | | | | | a) Add comments to test_4() in test/external.c about the name "/ link". b) Fix one memory leak in src/H5Lexternal.c: free memory pointed to by tmp_env_prefix for HDF5_EXT_PREFIX case. 3. Made changes for bug #1930 as in rev #19783, #19781 in trunk. 4. Made corresponding CMake changes as in rev #19782 in trunk.
* [svn-r19618] Purpose:Mike McGreevy2010-10-151-22/+31
| | | | | | | | | | Bring metadata accumulator fixes and tests into 1.8 Description: Changes consist of addition of tests for H5Faccum.c source code, as well as some fixes that address some discovered bugs in the metadata accumulator on several corner cases. Tested: h5committested
* [svn-r19408] In this revision the '/' after ${DESTDIR} wherever it occursLarry Knox2010-09-161-5/+15
| | | | | | | | | | | | | | | | | | | | has been removed. According to the official description of DESTDIR by Gnu at http://www.gnu.org/prep/standards/html_node/DESTDIR.html, DESTDIR is prepended to the normal and complete install path that it precedes for the purpose of installing in a temporary directory which is useful for building rpms and other packages. The '/' after ${DESTDIR} will be followed by another '/' at the beginning of the normal install path. When DESTDIR is empty the path then begins with '//', which is incorrect and causes problems at least for Cygwin. The change made in config/commence.am affects many Makefile.*s when bin/reconfigure is run. EXAMPLEDIRs had to be corrected individually. Also the scripts to run examples after they are installed have checks added to see that the fortran and c++ directories are present before trying to run the scripts in them. Tested with h5committest on amani, heiwa and jam.
* [svn-r19405] Description:Quincey Koziol2010-09-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | Bring r19402 from trunk to 1.8 branch: Correct Bz#1968 (Problem when opening new format file with H5F_LIBVER_EARLIEST) by initializing symbol table leaf information in a more universal way. Also cleaned up other superblock initialization a little bit while I'm here. Tested on: FreeBSD/32 6.3 (duty) in debug mode FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, w/threadsafe, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in debug mode Mac OS X/32 10.6.4 (amazon) in debug mode Mac OS X/32 10.6.4 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode Mac OS X/32 10.6.4 (amazon) w/parallel, in debug mode
* [svn-r19371] Updated autoconf to version 2.6.7, libtool to version 2.2.10, ↵Larry Knox2010-09-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and m4 to version 1.4.14. Also added m4 directory for m4 macros according to autoconf suggestion. Tested with h5committest on amani, jam, and heiwa, and on linew. -This line, and those below, will be ignored-- M hdf5_1_8/test/Makefile.in A hdf5_1_8/m4 AM hdf5_1_8/m4/ltsugar.m4 AM hdf5_1_8/m4/libtool.m4 AM hdf5_1_8/m4/ltversion.m4 AM hdf5_1_8/m4/lt~obsolete.m4 AM hdf5_1_8/m4/ltoptions.m4 M hdf5_1_8/configure M hdf5_1_8/Makefile.in M hdf5_1_8/testpar/Makefile.in M hdf5_1_8/configure.in M hdf5_1_8/src/Makefile.in M hdf5_1_8/tools/Makefile.in M hdf5_1_8/tools/misc/Makefile.in M hdf5_1_8/tools/h5dump/Makefile.in M hdf5_1_8/tools/h5repack/Makefile.in M hdf5_1_8/tools/h5jam/Makefile.in M hdf5_1_8/tools/h5diff/Makefile.in M hdf5_1_8/tools/lib/Makefile.in M hdf5_1_8/tools/h5copy/Makefile.in M hdf5_1_8/tools/h5import/Makefile.in M hdf5_1_8/tools/h5stat/Makefile.in M hdf5_1_8/tools/h5ls/Makefile.in M hdf5_1_8/hl/test/Makefile.in M hdf5_1_8/hl/tools/Makefile.in M hdf5_1_8/hl/tools/gif2h5/Makefile.in M hdf5_1_8/hl/Makefile.in M hdf5_1_8/hl/src/Makefile.in M hdf5_1_8/hl/c++/test/Makefile.in M hdf5_1_8/hl/c++/Makefile.in M hdf5_1_8/hl/c++/src/Makefile.in M hdf5_1_8/hl/c++/examples/Makefile.in M hdf5_1_8/hl/fortran/test/Makefile.in M hdf5_1_8/hl/fortran/Makefile.in M hdf5_1_8/hl/fortran/src/Makefile.in M hdf5_1_8/hl/fortran/examples/Makefile.in M hdf5_1_8/hl/examples/Makefile.in M hdf5_1_8/config/commence.am M hdf5_1_8/MANIFEST M hdf5_1_8/c++/test/Makefile.in M hdf5_1_8/c++/Makefile.in M hdf5_1_8/c++/src/Makefile.in M hdf5_1_8/c++/examples/Makefile.in M hdf5_1_8/bin/ltmain.sh M hdf5_1_8/bin/reconfigure M hdf5_1_8/perform/Makefile.in M hdf5_1_8/fortran/test/Makefile.in M hdf5_1_8/fortran/testpar/Makefile.in M hdf5_1_8/fortran/Makefile.in M hdf5_1_8/fortran/src/Makefile.in M hdf5_1_8/fortran/examples/Makefile.in M hdf5_1_8/aclocal.m4 M hdf5_1_8/examples/Makefile.in
* [svn-r19359] When mandatory filter failed to write data chunks, the datasetRaymond Lu2010-09-081-31/+39
| | | | | | | couldn't close (bug 1260). The fix releases all resources and closes the dataset but returns a failure. Tested with h5committest - jam, heiwa, amani.
* [svn-r19077] Purpose: Fix bug 1951Neil Fortner2010-07-161-14/+22
| | | | | | | | | | | | Description: A bug introduced in 1.8.5 causes local heap data blocks to be mis-aligned when sizeof_offsets + 2*sizeof_lengths is not a multiple of 8. In this case, the address of the data block as stored in the heap prefix is aligned but the actual data block is not. This causes files created with these sizes to be corrupted, and prevents uncorrupted files with these sizes to be unreadable. Modified local heap code to account for alignment. Tested: jam, amani, linew (h5committest)
* [svn-r18836] Added code to config files, libhdf5.settings.in and ↵Larry Knox2010-05-171-0/+2
| | | | | | configure.in to add compiler version information for fortran and C++ in the settings file and the configure output for our common compilers on linux, solaris, and mac(gnu only). Tested: amani, jam, linew (h5committest) and with configure on these machines and tejeda.
* [svn-r18779] Add ${DESTDIR} to scripts and Makefiles so that make ↵Larry Knox2010-05-121-5/+5
| | | | | | DESTDIR=<install directory> install, installcheck and uninstall is supported for installing examples, since they are now installed as part of make install. This was necessary for rpmbuilds, but should also be supported otherwise. Tested: amani, jam, linew with committest, rpmbuild on jam and amani.
* [svn-r18710] Purpose:Mike McGreevy2010-05-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | 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 is being deprecated in favor of the --enable-largefile flag (enabled by default), which can be used on all platforms. --disable-linux-lfs can still be used to disable largefile support (on linux) when the --enable-largefile flag is not specified. 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-r18701] ID 1853:Albert Cheng2010-05-041-0/+1
| | | | | | | | Added the configure option --enable-h5dump-packed-bits for the h5dump optional feature. Tested: Jam (default and --disable-h5dump-packed-bits).
* [svn-r18580] 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-r18422] Description:Quincey Koziol2010-03-181-4/+8
| | | | | | | | | | | | | | | | | | | | | | | Bring r18413:18420 from trunk to 1.8 branch: - unify srcdir query, etc. - Move libhdf5.settings string out of H5Tinit.c 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.2 (amazon) in debug mode Mac OS X/32 10.6.2 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r18189] I added a test for copying an existing DCPL and using the copy ↵Raymond Lu2010-01-291-5/+6
| | | | | | | | | | to create a new dataset. There's a bug report (#1608) saying h5repack failed to do that sometimes. But I couldn't reproduce it. So I added this test and closed the report. The test is in the function test_copy_dcpl in dsets.c. Tested on jam, amani, and linew.
* [svn-r18106] bug 1673:Albert Cheng2010-01-121-5/+5
| | | | | | | | | | | | | | The mixed use of RUNTEST (original) and RUNTESTS (new) caused confusion. E.g., the timings in test/ was still using the old $RUNTEST. It made more sense to use $RUNTEST which is used by the dejagnu feature of automake. So, I changed all $RUNTEST or $RUNTESTS to $RUNEXEC. config/commence.am & config/conclude.am are the two files that got changes. Also fixed an error in test/Makefile.am. The rest are changed by bin/reconfigure. Tested: h5committested.
* [svn-r17645] Purpose:Mike McGreevy2009-10-151-7/+14
| | | | | | | | | | | | | | | Merge from Trunk Description: Merging all of my CFLAGS-related changes from trunk to 1.8 This includes revision #s: 17616, 17625, 17627, 17639, and 17643. Tested: h5committest and some additional checks on our FreeBSD as well as NCSA's machines.
* [svn-r17579] added testlibinfo.sh testcheck_version.sh to be distcleaned.Albert Cheng2009-10-011-1/+1
| | | | Test: Jam.
* [svn-r17548] ↵Albert Cheng2009-09-291-10/+22
| | | | | | | | | | | | | | | | ------------------------------------------------------------------------ r17543 | acheng | 2009-09-28 23:43:22 -0500 (Mon, 28 Sep 2009) | 8 lines New test: (Bug ID 1656): Add new tests (tcheck_version, testcheck_version.sh) to verify H5check_version() does issue warnings and abort accordingly. Changed H5check_version() to suppress the warning message totally if $HDF5_DISABLE_VERSION_CHECK is 2 or higher. (Old behavior treated 3 or higher the same as 1, that is to print a warning and allows the program to continue. Tests: H5committed tested plus jam serial tested.
* [svn-r17540] Snapshot version 1.8 release 3 (snap12)Larry Knox2009-09-271-5/+5
|
* [svn-r17526] Description:Quincey Koziol2009-09-241-6/+14
| | | | | | | | | Add backward compatibility test to make certain that the 1.8 library handles encountering a file with a fixed array chunk index gracefully. Tested on: FreeBSD/32 6.3 (duty) w/production (too minor to require h5committest)
* [svn-r17517] In the function test_rw_noupdate, I added a test with the ↵Raymond Lu2009-09-241-5/+5
| | | | | | | | | | | system functions to make sure the stat function behaves as we expected. This test is skipped on some system because the modification time from stat is the same as the last access time (We know OpenVMS behaves in this way). Tested on jam. I've tested the same change for the trunk on jam, smirom, and linew. My account for OpenVMS expired. I'll test it once I have it back.
* [svn-r17499] Purpose:Albert Cheng2009-09-181-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Stage 2 implementation of embedded library information feature. H5.c: added code to print the embedded library information when there is a library versions mis-match occurs. This ensures the library information string is included in the executable. Also modifies the code so that the Library mismatch warning string is included only once in the executable. H5private.h: Added a global reference to the libinfo string variable to prepare for possible stage 3 implementation of a public API. test/testlibinfo.sh.in: A new test added to verify the library information is indeed included in the executables. configure.in: configure: Added entry to auto-generate test/testlibinfo.sh. H5detect.c: Modified the libhdf5settings generating code to allow it to insert the strings to a file other than stdout. This maybe needed in stage 3 implementation. MANIFEST: updated with the newly added file of testlibinfo.sh.in. Tested: h5committest passed. Also passed jam in serial mode.
* [svn-r17439] Purpose:Mike McGreevy2009-08-311-33/+69
| | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Bring revisions 17345 and 17357 from trunk to 1.8, specifically: - 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). - bin/install-sh script replaced with new version as provided by automake. Tested: - All issues on trunk were resolved, so only tested on jam and linew. Any other outliers should be caught by daily tests.
* [svn-r16993] Snapshot version 1.8 release 3 (snap0)Larry Knox2009-06-011-18/+18
|
* [svn-r16920] Description:Quincey Koziol2009-05-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge these trunk revisions which occurred during the 1.8.3 release code freeze back to the 1.8 branch: From Quincey: 16845 16847 16849 16851 16858 16869 16897 From Ray: 16859 16880 From Allen: 16863 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/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.6 (amazon) in debug mode Mac OS X/32 10.5.6 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r16793] Description:Mike McGreevy2009-04-201-10/+10
| | | | | | | | | | | | - Updated bin/reconfigure to use latest version of automake (1.10.2). Regenerated Makefile.in's by running bin/reconfigure. - Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran libraries. Tested: jam, liberty, smirom
* [svn-r16562] Purpose:Mike McGreevy2009-03-101-3/+3
| | | | | | | | | | | | | | | | | | Bug Fix Description: Fixing BZ #1381. The --includedir=DIR configure option, which is used to spceify installation location of C header files, did not work correctly as the path was hard-coded into config/commence.am. I'm presuming this is because an older version of automake didn't know where to put C header files. In any case, removing this line now defaults the includedir to the same directory that it is currently hard-coded to, and also fixes the configure flag which allows for customization of this value. Tested: jam, liberty
* [svn-r16519] merge 16518 from trunkPedro Vicente Nunes2009-02-261-13/+15
| | | | | | have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output) the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other tested: jam, linew
* [svn-r16398] Snapshot version 1.8 release 2 (post5)HDF Tester2009-02-011-2/+2
|
* [svn-r15898] Purpose: Bug FixMike McGreevy2008-10-171-6/+1
| | | | | | | | | | | | | | | Description: Libtool wasn't working on linew because the script was not working with the Solaris Bourne shell. Libtool has built- in detection to ensure that it uses an appropriate shell, but our config/commence.am was hard coding this shell to be /bin/sh. Removing this line allows the shell to be picked up by configure, thus allowing libtool to use the correct shell on linew (bash). This was initially added to correct for a problem on an old machine (janus), so shoudn't be needed for machines we currently support. Tested: full make check install on kagiso and linew, compile only on smirom, duty, and liberty.
* [svn-r15881] Purpose: Bug Fixes, Libtool UpgradeMike McGreevy2008-10-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Description: 1) configure now sets LD_LIBRARY_PATH before checking for presence of SZIP encoder, so user does not need to set this. The path is then saved and sent to Makefiles, and used when "make check-install" is invoked, so user doesn't need to set this manually. 2) Upgraded libtool to version 2.2.6a 3) Rearranged tools build order as h5dump depends on existence of h5diff and h5import. Since h5dump is a sister directory as opposed to a parent of either, it doesn't know about the build rules of these tools, so setting any sort of explicit dependency confuses automake as it won't know how to build the tools. Instead, setting CONFIG = ordered forces an in-order traversal of each tools subdirectory. (without it will also traverse in order by default, but this should prevent gmake's -j option from jumping ahead as well). 'make check install' should now be able to be invoked after 'configure' without causing a dependency failure. 4) Removed H5_HAVE_LARGE_HSIZET macro from vms/src/h5pubconf.h, as this macro has now been out of the code for some time. (vms pubconf needs to be updated manually, which is why it was still hanging around). Tested: kagiso, smirom, liberty Note: h5diff looks to be causing failures in h5copy and h5dump tools tests, though these were present before any of my changes. My changes only affect build order and configuration setup, and shouldn't prevent fixes for these failures coming in after this checkin. Other than these, tests pass fine.
* [svn-r15811] Some test produced files were not cleaned by "make clean".Albert Cheng2008-10-081-5/+5
| | | | | | Added them to the clean list. Tested: kagiso.
* [svn-r15801] Description:Quincey Koziol2008-10-071-18/+35
| | | | | | | | | | | | | | | | | | | | | | | Bring r15800 back from trunk: - File free space branch changes through r15794 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-r15486] Purpose: Allow library to shut down properly when objects have ↵Neil Fortner2008-08-191-12/+21
| | | | | | | | | | | | | | | | reference count > 1. Description: Added a new field 'app_count' to H5I_id_info_t struct, to track the reference count on an id due to the application. the old 'count' field tracks the total. Generally any id visible to the application gets placed in app_count. Added app_ref boolean parameter to H5I_inc_ref, H5I_dec_ref, H5I_register, H5I_clear_type, and a few other functions, to specify whether the operation(s) being performed on the id(s) are due to the application (TRUE) or not (FALSE). Test added for this case. Tested: kagiso, smirom, linew (h5committest)
* [svn-r15042] Bug fix.Albert Cheng2008-05-201-4/+4
| | | | | | | | | | | | | | | | | | | Description: The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the Fortran API source so that conclude.am will give fortran api prefix in the test output. The symbox HDF_FORTRAN is also used in configure for a different purpose (indicated --enable-fortran). They conflicted. Similar problem for the symbol HDF_CXX. Solution: Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is a more appropriate name. Same for CXX_API. Along the way, discovered that the Makefile.am of hl/fortran/test and hl/cxx/test did not have those symbols at all. Added them in. Platform tested: Kagiso serial and h5committested (kagisopp, smirom, linew).
* [svn-r15033] Purpose:Albert Cheng2008-05-191-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improvement. Description: src/libhdf5.settings was the initial configure summary and is installed. Then configure is changed to dump a summary of the configure settings to the output and also append it to src/libhdf5.settings. That created two different output formats and duplicated information. This is the initial attempt to clean up this confusion and unify the output format. It is decided to use the src/libhdf5.settings template as the unified means. This requires more macros symbols be defined. The following symbols are all related to generating the src/libhdf5.settings file. AC_SUBST(EXTERNAL_FILTERS) AC_SUBST(MPE) MPE=no AC_SUBST(STATIC_EXEC) STATIC_EXEC=no AC_SUBST(HDF_FORTRAN) HDF_FORTRAN=no AC_SUBST(FC) HDF_FORTRAN=no AC_SUBST(HDF_CXX) HDF_CXX=no AC_SUBST(CXX) HDF_CXX=no AC_SUBST(HDF5_HL) HDF5_HL=yes AC_SUBST(GPFS) GPFS=no AC_SUBST(LINUX_LFS) LINUX_LFS=no AC_SUBST(INSTRUMENT) INSTRUMENT=no AC_SUBST(CODESTACK) CODESTACK=no AC_SUBST(HAVE_DMALLOC) HAVE_DMALLOC=no AC_SUBST(DIRECT_VFD) DIRECT_VFD=no AC_SUBST(THREADSAFE) THREADSAFE=no AC_SUBST(STATIC_SHARED) AC_SUBST(enable_shared) AC_SUBST(enable_static) AC_SUBST(UNAME_INFO) UNAME_INFO=`uname -a` The src/libhdf5.settings.in has CONDITIONAL's added to it too. The untrue conditions turned into a "#" and these lines are cleaned by the post processing script. Platform tested: h5committest on kagiso, smirom and linew. (smirom had failures not due to my changes.)
* [svn-r15019] Mike McGreevy2008-05-161-13/+13
| | | | | | | | | | | Purpose: Configure Fix Description: The test program h52gifgentst was getting installed in the bin directory during 'make install', and it shouldn't. Make now builds the program for use in testing but doesn't install it during 'make install'. Tested: kagiso
* [svn-r15006] Purpose: configure cleanupMike McGreevy2008-05-151-1/+0
| | | | | | | Description: cleaning up configure related to removal of --disable-hsizet flag, which we no longer support. Tested: kagiso
* [svn-r14931] Snapshot version 1.8 release 0 (snap5)HDF Tester2008-05-051-13/+15
|
* [svn-r14824] Purpose: Updating HDF5 1.8 to use automake 1.10.1 and ↵Mike McGreevy2008-04-101-14/+18
| | | | | | | | | | | | | | | | | | libtool 2.2 Description: Updated bin/reconfigure script to reflect the new versions of libtool and automake in the /home1/packages/ directory. Rearranged configure.in script. For some reason, when using libtool 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, tg-login
* [svn-r14791] Add handling for external link:Vailin Choi2008-04-021-2/+2
| | | | | | | 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-17/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-r14385] This checkin completely modified the test for the coordinate ↵Raymond Lu2008-01-091-2/+2
| | | | | | | | calculation of dataspace selection. It covers many cases. Tested on smirom, kagiso, and linew.
generated by cgit v0.12 at 2024-10-30 04:01:23 (GMT)