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.
------- Forwarded Message Date: Thu, 01 Nov 2001 09:26:51 -0700 From: Russ Rew <address@hidden> To: "Glenn Rutledge" <address@hidden> cc: steve Subject: Re: 20011031: Make Install err w/ netCDF >To: Russ Rew <address@hidden> >From: "Glenn Rutledge" <address@hidden> >Subject: Make Install err w/ netCDF >Organization: NCDC >Keywords: 200110312009.f9VK9k117932, Fortran90, module files Glenn, > Since I'm not sure which of the files needs to be copied (and where they > need to be copied to), here's a listing. Which one (netcdf.M?), and where > to I need to put it? Thanks, Glenn It looks like you need to copy both netcdf.M and typesizes.M -rw-rw-r-- 1 noaaport 2383 131844 Oct 31 14:58 netcdf.M -rw-rw-r-- 1 noaaport 2383 1532 Oct 31 14:56 typeSizes.M to your installation include/ directory. This is the first f90 compiler I've seen that uses the ".M" extension for module files. I'm curious what platfrom you ran this on. Just copy the above files directly to the installation include/ directory, and hopefully that will permit Fortran90 programs to get at the modules with use typeSizes use netcdf statements at the top of programs that make use of these modules. For a future release, we'll have to figure out a way to determine what extension the Fortran 90 compiler uses (so far we've seen ".mod", ".Mod", ".MOD", and now ".M") and make this automatic ... --Russ ------- End of Forwarded Message