summaryrefslogtreecommitdiffstats
path: root/examples/testh5cc.sh.in
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r22724] Convert tests to *.sh.in.Allen Byrne2012-08-281-5/+2
| | | | | | | | Convert configure.in to configure.ac. Align TESTS usage with autotools convention. Update all references from configure.in to configure.ac Tested: h5committest
* [svn-r21547] Updated svnprops on many files, mainly for EOL issues.Dana Robinson2011-10-131-0/+0
| | | | No testing since there are no code changes.
* [svn-r19408] In this revision the '/' after ${DESTDIR} wherever it occursLarry Knox2010-09-161-1/+2
| | | | | | | | | | | | | | | | | | | | 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-r18779] Add ${DESTDIR} to scripts and Makefiles so that make ↵Larry Knox2010-05-121-1/+1
| | | | | | 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-r18056] Bug fix: 1192Albert Cheng2009-12-261-4/+10
| | | | | | | | Description: Fixed exit code (sometimes return code in Main) to follow the HDF5 standards. Tested: Jam, both serial and parallel.
* [svn-r17769] Bug 1264 fixed.Albert Cheng2009-10-281-1/+89
| | | | | | | | | Tests to verify the bug fixed are installed. Test: v1.8.4 passed all tests on Jam (default and with --disable-depreacted-symbol), Amani (v16API), Linew (default). This should be good for v1.8 too.
* [svn-r17694] Removed the erroneous test of using v16 API.Albert Cheng2009-10-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | The error started out as an erroneous test of using v16 API via source code. (See bug 1264). It was implemented as: #include "hdf5.h" #define H5_USE_16_API That was incorrect and generated warnings in Linux but error in AIX for redefining macro H5_USE_16_API. I corrected it yesterday to pass AIX by moving H5_USE_16_API up as: #define H5_USE_16_API #include "hdf5.h" This is the proper way to turn on v16API and it passes all normal tests. I knew it would not work if somehow v16API is disabled but hoping it can be fixed later. Well, it broke last night under --disable-deprecated-symbols. Removed the #define H5_USE_16_API and let Raymond fix it after the release.
* [svn-r17686] Bug fix:Albert Cheng2009-10-201-2/+2
| | | | | | | | | | | #define H5_USE_16_API was inserted AFTER #include <hdf5.>, too late was it to take effect. Instead, it caused a macro redefinition, flagged as an error by AIX. Fixed by moving it before the <hdf5.h>. Tested: Jam.
* [svn-r16838] Bug fix:Albert Cheng2009-04-221-2/+2
| | | | | | | | | | | | | If the AR command has embedded shell separators such as the case of "AR = ar -X 64", $AR ends up as a blank. Solution: Put quotes around the command substitution string to protect against embedded separators. Applied the same to both AR and RANLIB assignments. Tested: At Up (AIX 5.3) only because that was where I discovered the error when AR is ar -X 64
* [svn-r15946] A follow-up checkin for the last-round commit(r15936). Added a ↵Raymond Lu2008-10-241-0/+1
| | | | | | | | | test in this script file to check whether the macros H5_USE_16_API works properly. There used to be a problem to compile if H5_USE_16_API is defined in the application program (see bug #1264). Tested on kagiso - simple change.
* [svn-r15712] Purpose:Albert Cheng2008-09-271-7/+31
| | | | | | | | | | features. Description: Added -shlib tests and verbosity control. Tested Platform: Kagiso.
* [svn-r13962] Purpose:Albert Cheng2007-07-101-1/+5
| | | | | | | | | | | | | | | | | | Bug fix. Description: It used to clean out all *.h5 when done but this could cause a racing condition error if parallel make (e.g., gmake -j ...) is used because the "rm ... *.h5 ..." would remove *.h5 generaged and are still used by other test programs (e.g. h5_write/h5_read). Solution: Removed "*.h5" from the cleanup list since the test program has already taken care of removing temporary *.h5 generated. Tested platform: Kagiso, both serial and parallel. Not triple platforms tested since this is just a simple shell script change.
* [svn-r13818] Bug fix.Albert Cheng2007-05-301-1/+1
| | | | | | | | | The test scripts did not take in account that the binary has been installed somewhere other than the original prefix. Added a provision to allow explicit definition of $prefix to work. Tested: kagiso.
* [svn-r13646] Fortran/examples/testh5fc.sh.in:Albert Cheng2007-04-111-7/+12
| | | | | | | | | | | | | Most fortran compilers do not support the Preprocessing -E option. Removed the tests for preprocessing only. examples/testh5cc.sh.in: c++/examples/testh5c++.sh.in: Updated comments and some cosmetic rearrangement. No substance changes. Tested platform: Copper, kagiso.
* [svn-r13633] PurposeAlbert Cheng2007-04-111-0/+228
New feature Description: Added test scripts to test the compiler scripts (h5cc, h5fc and h5c++) Tested platform: Kagiso (serial and pp)