[netCDF #KQB-994701]: Old libnetcdf.a Library File

Hello Jim,

So it sounds like the version of netCDF you were using is old enough that it 
contained both the C and fortran interfaces combined.  Starting with netCDF 
4.2, the C and Fortran interfaces were split into separate libraries.  You 
should be able to download the C and Fortran source code from 
https://github.com/Unidata/netcdf-c/releases and 
https://github.com/Unidata/netcdf-fortran/releases and compile/install them.  
You will need to install the C library first, as the fortran interface depends 
upon it.  If you intend to use netCDF-4 functionality, you will also need to 
install the HDF5 library, but this isn't required unless you specifically need 
the extended data model and file format.

I hope this helps!

-Ward

> Full Name: Jim Secan
> Email Address: address@hidden
> Organization: NWRA
> Package Version:
> Operating System: macOS
> Hardware: iMac
> Description of problem:
> 
> I have a number of netCDF files built from 1999 through 2013 using the old
> Fortran netCDF interface based on the libnetcdf.a file.  These were all
> done on 32-bit Linux system.  I am trying to access these data, and the
> associated processing codes, but since I am now on more modern systems
> the old library file will not work with current compilers.  I am trying
> to avoid a multi-step process of using something like the ncks utility
> to reformat the netCDF into ASCII column files, and I am hoping that
> there may be a way to get a 64-bit version of the libnetcdf.a library
> which I can use with the gfortran compiler on a macOS-based machine.
> Is there some way I can get this library?
> 
> 


Ticket Details
===================
Ticket ID: KQB-994701
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.