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.
Dick, > To: address@hidden > From: address@hidden (Dick Valent) > Subject: unsatisfied external > Organization: UCAR/NCAR/SCD > Keywords: 199607021922.AA28436 In the above message you wrote: > On SCD's CRAY PVP systems, I compile a small Fortran code, just to > check the installation procedure. > > INCLUDE '/usr/local/include/netcdf.inc' > NC = NCCRE(PATHNAME, CMODE, rcode) > CALL NCCREDF(NCID, rcode) > CALL NCINQ(NCID, ndims, nvars, natts, recdim, rcode) > STOP > END > > I use cf77 invokation > > cf77 job.f -L/usr/local/lib -lnetcdf > > The compiler returns this diagnostic: > > > ldr-133 cf77: CAUTION > > Unsatisfied external references have been encountered. > > Entry name Modules referencing entry > > NCCREDF $MAIN > > I am wondering if subroutine NCCREDF is a valid netCDF routine name? NCCREDF is not a valid netCDF FORTRAN routine. The routine you want is, undoubtably, NCREDF (with only one `C'). > Neither NCCRE nor NCINQ are flagged as unsatisfied externals. I obtained > all three names from "man 3f netcdf" That's a typo in the manual page (which I'm about to fix). Sorry 'bout that. -------- Steve Emmerson <address@hidden> >From address@hidden Tue Jul 2 07:31:44 1996 >Regarding the e-mail I sent a few minutes ago: I think I found >the answer to my question. The routine name in question is >NCREDF rather than NCCREDF as stated in the man page. I determined >this by looking at Appendix B of the User's Guide. >Thanks, --Dick Valent