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.
Brian, >Date: Fri, 11 Jun 1999 15:39:34 -0800 >From: address@hidden >Organization: NOAA >To: address@hidden >Subject: Re: 19990607: nf_test for netcdf-3.4 >Keywords: 199906070237.UAA21584 In the above message, you wrote: > I've decide to go with just the C language because the test still fails and > there's too many warnings in the make with g77 added to deal with. Thanks for > your nevertheless. Attachments for your information. OK. If, in the future, you want to take another stab at creating the Fortran interface using g77(1), then ensure that the FFLAGS environment variable contains the "-Wno-globals" option. This should eliminate the warnings you encountered like the following: > Making `test' in directory /export/trichodon2/gmt/netcdf-3.5/src/fortran=0D= > > =0D > + /usr/local/bin/g77 -c -O ftest.F =0D > ftest.F: In subroutine `tncacpy':=0D > ftest.F:187: warning:=0D > call ncagt (outcdf, NCBYTE, attnam, bytval, iret)=0D > 1=0D > ftest.F:196: (continued):=0D > call ncagt (outcdf, NCGLOBAL, attnam, shval, iret) =0D > 2=0D > Argument #4 of `ncagt' is one precision at (2) but is some other = > precision at (1) [info -f g77 M GLOBALS]=0D > ftest.F:187: warning:=0D > call ncagt (outcdf, NCBYTE, attnam, bytval, iret)=0D > 1=0D > ftest.F:198: (continued):=0D > call ncagt (outcdf, NCGLOBAL, attnam, lngval, iret) = > = > > 2=0D > Argument #4 of `ncagt' is one precision at (2) but is some other = > precision at (1) [info -f g77 M GLOBALS]=0D ... -------- Steve Emmerson <http://www.unidata.ucar.edu>