> My netcdf is successfully installed however while installing WRF v 3.6.1 it > is showing some error in netcdf installation > The message was, > Error : Not found /usr/local/include/netcdf.inc > Please check this installation of NetCDF and re-run this configure script > > scientific linux 6.5 x64, gcc with gfortran The netcdf.inc file is part of the netCDF-Fortran installation. I'm guessing you only installed the netCDF-C library, which is needed for the netCDF-Fortran library, but you still have to download and install the netCDF-Fortran software, and follow these instructions: Building the NetCDF-4.2 and later Fortran libraries http://www.unidata.ucar.edu/netcdf/docs/building_netcdf_fortran.html It's probably easiest to build and install the most recent version 4.4.0 of netCDF-Fortran, available here: http://www.unidata.ucar.edu/downloads/netcdf/ Please let us know if you encounter problems. --Russ > ----- Original Message ----- > > From: "Unidata netCDF Support" <address@hidden> > To: address@hidden > Cc: address@hidden, address@hidden > Sent: Tuesday, September 2, 2014 8:47:42 PM > Subject: [netCDF #MBG-731605]: Problem installing netcdf v3.3.1.1 > > This is a known issue related to a change in our test server > configuration since version 4.3.1.1. The 4.3.2 release fixes it by > pointing directly to our new test servers. So, the failure is on our > end, not yours. > > With version 4.3.1.1, you can complete testing and installation of > the netCDF C library and utilities by following these steps: > > 1. Run "make clean" in the top level directory of your source netCDF > source (or unpack the source again in a new source directory) > > 2. Run the "configure" script again, but this time add the following > option to whatever options you previously specified: > > --disable-dap-remote-tests > > 3. Run "make check" and verify that it now completes successfully. > > 4. Run "make install", or "sudo make install" if needed. > > That should get you past the problem with our test server and allow > the installation to complete successfully. Please let us know if you > encounter additional errors. > > --Russ > > > Please find the attached entire "make check install" log. > > > > There were two failures in tests. Following are the last few lines. (Also > > in error message file) > > > > > > PASS: tst_ncdap3.sh > > FAIL: tst_remote3.sh > > PASS: tst_formatx.sh > > PASS: t_dap3a > > PASS: test_cvt3 > > PASS: test_vara > > PASS: test_partvar > > PASS: test_varm3 > > PASS: test_nstride_cached > > FAIL: t_auth > > PASS: t_misc > > make[6]: Entering directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make all-recursive > > make[7]: Entering directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > Making all in testdata3 > > make[8]: Entering directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/testdata3' > > make[8]: Nothing to be done for `all'. > > make[8]: Leaving directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/testdata3' > > Making all in expected3 > > make[8]: Entering directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expected3' > > make[8]: Nothing to be done for `all'. > > make[8]: Leaving directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expected3' > > Making all in expected4 > > make[8]: Entering directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expected4' > > make[8]: Nothing to be done for `all'. > > make[8]: Leaving directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expected4' > > Making all in expectremote3 > > make[8]: Entering directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expectremote3' > > make[8]: Nothing to be done for `all'. > > make[8]: Leaving directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expectremote3' > > Making all in expectremote4 > > make[8]: Entering directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expectremote4' > > make[8]: Nothing to be done for `all'. > > make[8]: Leaving directory > > `/opt/softwares/netcdf-4.3.1.1/ncdap_test/expectremote4' > > make[8]: Entering directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[8]: Nothing to be done for `all-am'. > > make[8]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[7]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[6]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > ============================================================================ > > Testsuite summary for netCDF 4.3.1.1 > > ============================================================================ > > # TOTAL: 12 > > # PASS: 10 > > # SKIP: 0 > > # XFAIL: 0 > > # FAIL: 2 > > # XPASS: 0 > > # ERROR: 0 > > ============================================================================ > > See ncdap_test/test-suite.log > > Please report to address@hidden > > ============================================================================ > > make[5]: *** [test-suite.log] Error 1 > > make[5]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[4]: *** [check-TESTS] Error 2 > > make[4]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[3]: *** [check-am] Error 2 > > make[3]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[2]: *** [check-recursive] Error 1 > > make[2]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make[1]: *** [check] Error 2 > > make[1]: Leaving directory `/opt/softwares/netcdf-4.3.1.1/ncdap_test' > > make: *** [check-recursive] Error 1 > > > > > > > > ----- Original Message ----- > > > > From: "Unidata netCDF Support" <address@hidden> > > To: address@hidden > > Cc: address@hidden > > Sent: Friday, August 29, 2014 1:54:20 AM > > Subject: [netCDF #MBG-731605]: Problem installing netcdf v3.3.1.1 > > > > > I have tried to install netcdf in a new Pc and there were some errors > > > while installation. > > > I have also attached the log file. > > > > The config.log you attached didn't indicate any build errors. It completed > > successfully after building all the necessary Makefiles. Error messages > > in config.log from a successful configure can be ignored, as they result > > from determining properties of the platform and d3evelopment environment > > needed to generate the necessary Makefiles. > > > > The test-suite.log file you attached also didn't seem to indicate any > > errors, > > though I'm not sure what the final line > > > > .. contents:: :depth: 2 > > > > meant. Did "make check" complete without any actual errors? Warnings and > > XFAIL messages about expected failures can be ignored. > > > > If "make check" didn't complete, then please send us its output, including > > whatever error message was emitted when it stopped. > > > > > > --Russ > > > > Russ Rew UCAR Unidata Program > > address@hidden http://www.unidata.ucar.edu > > > > > > > > Ticket Details > > =================== > > Ticket ID: MBG-731605 > > Department: Support netCDF > > Priority: Normal > > Status: Closed > > > > > > > > > > -- > > --------------------------------------------------------------------- > > Thanks and Regards > > --------------------------------------------------------------------- > > Piyush Bhardwaj > > SRF, Atmospheric Science Division > > ARIES Manora Peak, Nainital-263002 > > Uttarakhand, India. > > > > > > Russ Rew UCAR Unidata Program > address@hidden http://www.unidata.ucar.edu > > > > Ticket Details > =================== > Ticket ID: MBG-731605 > Department: Support netCDF > Priority: Normal > Status: Closed > > > > > -- > --------------------------------------------------------------------- > Thanks and Regards > --------------------------------------------------------------------- > Piyush Bhardwaj > SRF, Atmospheric Science Division > ARIES Manora Peak, Nainital-263002 > Uttarakhand, India. > Tel:+91-5942-233734, 233735, 233727, 232655, Ext: 147 > Fax:+91-5942-233439 > --------------------------------------------------------------------- > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: MBG-731605 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.