This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
> > Dear Sirs: > > With netCDF Version 4.1.x, I am having a _lot_ of problems > from the environmental community's use of the Models-3 I/O API > data access library, which is built on a number of lower-level > platforms including netCDF and PVM3. This library has been in > extensive use in the environmental modeling community since > 1993, and is the official data access library for the EPA's > emissions and Eulerian air quality models. > > Suddenly, all of the model-building and tool-building > facilities are breaking: whereas previous versions of > libnetcdf.a stood alone, now new libraries, including > particularly libnetcdff.a, are required -- making it > impossible to construct a Makefile that works simultaneously > for netCDF v3.x and v4.x. > > At least with the other extra libraries (HDF, etc., it is > possible to configure the netCDF build so as to turn off > these features. How can my community configure it to > construct a _single_ C-and-Fortran "libnetcdf.a" ?? > > Sincerely, > > > Carlie J. Coats, Jr., Ph.D. > > EPA/BAMS/MCNC Models-3 I/O API Systems Architect > > Chief Systems Architect address@hidden > Environmental Modeling Center address@hidden > Baron Advanced Meteorological Systems, LLC. > > 1021 Main Campus Drive, Suite 300 campux box 7268 > Raleigh, NC 27606 phone: (919)515-0762 / fax: (919)515-0767 > > Howdy Carlie! I have a hard time understanding why it is so difficult to modify Makefiles to use -lnetcdff instead of -lnetcdf. What am I missing here? Thanks, Ed Ticket Details =================== Ticket ID: KGN-827851 Department: Support netCDF Priority: Normal Status: Closed