[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #IXF-589871]: help installing netcdf

> This is hoping I can find someone to help. I have been trying to
> install netcdf for over a month without success. I eventually
> installed with "--disable-netcdf-4"t in order to install WRF. WRF
> works but I cannot handle grib2 data, hence the need to reinstall
> netcdf with hdf support. ...

Sorry to hear netCDF installation is not working for you.

I don't understand why you need netcdf-4 to handle grib2 data.  The
C-based netcdf-4 release doesn't handle grib2 data on a local disk,
just netCDF classic data, netCDF-4 data, some HDF4 and HDF5 data.  Are
you trying to access grib2 data from a remote server through the DAP
protocol built into netcdf-4?  If so, we'll need more information
to try to diagnose the problem you're seeing.

>                      ... hdf apparently installed cleanly, but with
> netcdf I get the message below:
> checking for library containing H5Fflush... no
> configure: error: Can't find or link to the hdf5 library. Use
> --disable-netcdf-4, or see config.log for errors.

There are a number of problems that could cause that error, including
having HDF5 installed for a different architecture (e.g. 32-bit
instead of 64-bit) than specified for the netCDF library, not setting
LD_LIBRARY_PATH to include the directory where HDF5 is installed, etc.

It would be helpful if you could send us the information requested here:


> The config.log file has errors like below:
> configure:14222: $? = 0
> configure:14444: result: GNU/Linux ld.so
> configure:14551: checking how to hardcode library paths into programs
> configure:14576: result: immediate
> configure:15116: checking whether stripping libraries is possible
> configure:15121: result: yes
> configure:15156: checking if libtool supports shared libraries
> configure:15158: result: yes
> configure:15161: checking whether to build shared libraries
> configure:15182: result: yes
> configure:15185: checking whether to build static libraries
> configure:15189: result: yes
> configure:15212: checking how to run the C++ preprocessor
> configure:15239: g++ -E conftest.cpp
> configure:15239: $? = 0
> configure:15253: g++ -E conftest.cpp
> conftest.cpp:38:28: fatal error: ac_nonexistent.h: No such file or directory
> compilation terminated.
> configure:15253: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "netCDF"
> | #
> The error with ac_nonexistent.h appears several times in config.log.
> I have sent just a small chunk so as not to overburden people, but if
> necessary I can send the whole config.log file.

Even for a successful installation, there are many error messages in
config.log, as a result of tests run to determine the properties of
the compile environment.  Errors in the output of configure, such as
the H5flush error above, actually indicate a problem, which is usually
identified by looking at the end of the corresponding config.log file
to see the deatiled error message.  For this, we need the entire output
of configure and the entrie config.log file.

> I have tried all sorts of entries in my shell environment without success.
> How do I make configure find the netcdf library path?

For version 4.1.3, you typically need to set LD_LIBRARY_PATH if
libraries are installed in a place that the compilers don't
automatically look in.  Some of this also depends on whether you are
installing shared libraries (recommended) or static libraries
(specifying --disable-shared to the configure script).  We might be
able to figure this out with the information in the link requested


Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu

Ticket Details
Ticket ID: IXF-589871
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.