> Are there any hdf5-1.8.4 patch1 with pgcc or pgf90? You don't need an HDF5 built with pgf90, as netCDF provides a fortran-90 API that doesn't depend on the HDF5 Fortran API. It is possible to build the HDF5 library with pgcc by just setting the environment variable CC=pgcc, before running configure, but we don't have a binary distribution of HDF5 or netCDF built with pgcc. We still haven't figured out why your netCDF file is unreadable using the netCDF 4.0 or 4.0.1 releases. It's apparenttly not due to the older version of HDF5 you used, because I just rebuilt both 4.0 and 4.0.1 iusing HDF5-1.8.4-patch1, and the resulting ncdump programs reported "unrecognized format" in both cases. There were bug fixes in 4.1.1, but I can't find any that explain why the 4.1.1 library is able to open that netCDF file but the 4.0 and 4.0.1 libraries can't. --Russ > -----Original Message----- > From: Unidata netCDF Support [mailto:address@hidden > Sent: Monday, August 30, 2010 1:23 PM > To: SMITH, JONATHAN WYNN. (GSFC-6133) > Cc: address@hidden > Subject: [netCDF #FSI-652508]: netcdf-4 with hdf5 and zlib not compiling > > Hi Jonathan, > > > I have compiled netcdf4 with hdf5-1.8.2 and zlib-1.2.3. > > When linking the math library, the file that I have attached > > (qfed2.emiss.bc.005.20060505.nc) was unable to open with ncdump. > > I just tried an ncdump compiled with the current netCDF-4 version 4.1.1 on > your file, and it > seems to work fine, with no errors reported. However, I got the same error > message you did, > "NetCDF: Unknown file format", when using ncdump from netCDF versions 4.0 or > 4.0.1. This is > puzzling, because the only bug I'm aware of with netCDF-4 compatibility is > with files written > with a variable with more than 8 attributes on a big-endian platform using a > version of HDF5 > prior to 1.8.4-patch1. Your file has no such variable, so it should be > readable. > > However, you can certainly work around the problem by installing the current > release, using > HDF5 1.8.4-patch1 or later for the underlying HDF library. > > In the meantime, we'll investigate further to see why that netCDF file is not > readable with > earlier versions of netCDF. Thanks for reporting this problem. > > --Russ > > > -----Original Message----- > > From: Unidata netCDF Support [mailto:address@hidden > > Sent: Thursday, August 26, 2010 12:41 PM > > To: SMITH, JONATHAN WYNN. (GSFC-6133) > > Cc: address@hidden > > Subject: [netCDF #FSI-652508]: netcdf-4 with hdf5 and zlib not compiling > > > > > Hello > > > So I saw the -lm should be set in the path for LIBS in the .bashrc file. > > > > > > netcdf 4 installed with no problem. Now the ncdump is not functioning. > > > See below attempt and error message below: > > > > > > ncdump -h qfed2.emis_co.005.20060620.nc > > > ncdump: qfed2.emis_co.005.20060620.nc: NetCDF: Unknown file format > > > > > > Jonathan > > > Jonathan Wynn Smith > > > Student Trainee > > > address@hidden > > > NASA/Goddard Space Flight Center > > > Code 613.3 - Atmospheric Chemistry and Dynamics Branch > > > Greenbelt, MD 20771 > > > 301-614-5956 > > > > > > Doctoral Candidate > > > address@hidden > > > Howard University Program in Atmospheric Sciences > > > Washington, DC 20059 > > > > > > > Howdy Jonathan! > > > > ncdump is telling you that the data file is not a netcdf data file. > > > > If you think it is a netcdf datafile, make sure the ncdump you are using is > > the one you just built, not some old one installed on your machine. > > > > Thanks, > > > > Ed > > > > Ticket Details > > =================== > > Ticket ID: FSI-652508 > > Department: Support netCDF > > Priority: Normal > > Status: Closed > > > > > > Russ Rew UCAR Unidata Program > address@hidden http://www.unidata.ucar.edu > > > > Ticket Details > =================== > Ticket ID: FSI-652508 > Department: Support netCDF > Priority: Normal > Status: Closed > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: FSI-652508 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.