3.6 Testing the Build
Run “make check” to verify that the netCDF library and executables
have been built properly (you can instead run “make test” which does
the same thing).
A make check will build and run various test programs that test the C,
Fortran, and C++ interfaces as well as the "ncdump" and "ncgen"
utility programs.
Lines in the output beginning with "***" report on success or failure
of the tests; any failures will be reported before halting the
test. Compiler and linker warnings during the testing may be ignored.
Run the tests like this:
make check
If you plan to use the 64-bit offset format (introduced in version
3.6.0) to create very large files (i.e. larger than 2 GB), you should
probably run “make extra_check which tests the large file
features. You must have 13 GB of free disk space for these tests to
successfully run.
If you are running make extra_check, you may wish to override the make
file variable TEMP_LARGE to specify a directory to which large files
can be written. The default is to create them in the nc_test
subdirectory of the netCDF build.
Run the large file tests like this:
make extra_check
Or, to specify a directory where the large files should be written
during the tests (the example below uses the /tmp directory):
make TEMP_LARGE=/tmp extra_check
If you have an environment variable TEMP_LARGE, the configure script
will tell the makefile to use that directory for large files.
All of the large files are removed on successful completion of
tests. If the test fails, you may wish to make sure that no large
files have been left around.
If any of the the large file tests test fail, run make check to run
additional large file tests, including a test which uses the dd
command to ensure that your file system can handle files larger than 2
GiB. This test runs the command:
dd if=/dev/zero bs=1000000 count=3000 of=$(TEMP_LARGE)/largefile
If your system does not have a /dev/zero, this test will fail. If all
other tests pass, this is if no concern, but if other tests fail, you
need to somehow ensure that your file system can handle very large
files.
These tests are slower; to run the slow large file tests:
make slow_check
This file system test can also be run by going into the directory
nc_test and making the target lfs_test. The target slow_check runs an
additional large file test, which writes about 4GiB of data to a file,
and then rereads it. Also in the nc_test directory, the target
all_large_tests will run all the large file tests.
See If Something Goes Wrong.
