Hi Shard, > Thanks for the reply. I have tried to find the reason, but enable to do so. > I have attached the error, which I got after make check.... ... > *** Testing netcdf file functions some more. > *** testing simple opendap open/close...Sorry! Unexpected result, > tst_files6.c, line: 25 > FAIL: tst_files6 ... > ================================================ > 1 of 50 tests failed > Please report to address@hidden > ================================================ > make: *** [check-TESTS] Error 1 > make: Leaving directory `/saral/softwares/netcdf-4.1.3/nc_test4' This is a problem with the configuration of the remote data test server used in the old and unsupported version 4.1.3, which has since been fixed to point to a new test server that will work correctly, so it's not a problem with your netCDF build. You can either choose 1. to complete the test and installation of version 4.1.3 after a "make clean" and rerunning configure and "make check", using the configure option "--disable-dap-remote-tests" or 2. Use the current supported release, version 220.127.116.11, and following the similar configure and build instructions here: http://www.unidata.ucar.edu/netcdf/docs/building.html I recommend approach 2, which also has fixes for other bugs in the 4.1.3 release. One difference is that version 18.104.22.168 has the Fortran support unbundled in a separate distribution, which you would need to build and install after installing the 22.214.171.124 netcdf C library, if you need the netCDF Fortran library. The downloads of the latest (126.96.36.199) C release and the 4.2 Fortran release are available here: http://www.unidata.ucar.edu/downloads/netcdf --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: OLR-692110 Department: Support netCDF Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.