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.
Carl, >Date: Mon, 26 Aug 1996 15:41:05 -0700 >From: address@hidden (Carl M. Lund) >Organization: Los Alamos National Laboratory >To: address@hidden >Subject: Installation with new xdrffio.c >Keywords: 199608221440.AA29398 In the above message you wrote: > Here's the whole installation attempt with the new xdrffio.c. > > Carl Lund > -------------------------------------------------------------------------------- > > > rho - 29 >setenv CC c89 > rho - 30 >setenv FC cft77 I think you should use the cf77(1) compiler rather than the cft77(1) one. ... > making `test' in directory /usr/tmp/cmlund/dnetcdf/netcdf-2.4.3/src/nctest > > c89 -o nctest -O varget.o vargetg.o varput.o varputg.o vardef.o vartests.o > vputget.o vputgetg.o driver.o cdftests.o dimtests.o rec.o atttests.o > misctest.o > add.o error.o emalloc.o val.o slabs.o ../libsrc/libnetcdf.a > ./nctest > *** Testing nccreate ... ok *** > *** Testing ncopen ... ok *** > *** Testing ncredef ... ok *** > *** Testing ncendef ... ok *** > *** Testing ncclose ... ok *** > *** Testing ncinquire ... ok *** > *** Testing ncsync ... ok *** > *** Testing ncabort ... ok *** > *** Testing ncdimdef ... ok *** > *** Testing ncdimid ... ok *** > *** Testing ncdiminq ... ok *** > *** Testing ncdimrename ... ok *** > *** Testing ncvardef ... ok *** > *** Testing ncvarid ... ok *** > *** Testing ncvarinq ... ok *** > *** Testing ncvarput1 ... ok *** > *** Testing ncvarget1 ... ok *** > *** Testing ncvarput ... ok *** > *** Testing ncvarget ... ok *** > *** Testing ncvarputg ... ok *** > *** Testing ncvargetg ... ok *** > *** Testing ncrecinq ... ok *** > *** Testing ncrecput ... ok *** > *** Testing ncrecget ... ok *** > *** Testing ncvarrename ... ok *** > *** Testing ncattput ... ok *** > *** Testing ncattinq ... ok *** > *** Testing ncattget ... ok *** > *** Testing ncattcopy ... ok *** > *** Testing ncattname ... ok *** > *** Testing ncattrename ... ok *** > *** Testing ncattdel ... ok *** > *** Testing nctypelen ... ok *** The above indicates that the library was built correctly. ... > making `test' in directory /usr/tmp/cmlund/dnetcdf/netcdf-2.4.3/src/fortran > > ar rcuv ../libsrc/libnetcdf.a jackets.o > : ../libsrc/libnetcdf.a > cft77 -c ftest.f > cft77-31 cft77: ERROR > -c option has an invalid argument t. I think the above is because the cft77(1) compiler is being used rather than the cf77(1) compiler. I suggest the following: 1. Go to the top-level source directory. 2. Ensure that the variable FC is unset, both in the environment and in the file CUSTOMIZE. 3. Remove the file `config.cache' if it exists. 4. Execute the `configure' script. 5. Execute the command `make'. 6. Execute the command `make test'. Please let me know if this helps. -------- Steve Emmerson <address@hidden>