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.
Dan, >Date: Mon, 30 Aug 1999 10:28:44 -0400 (EDT) >From: Dan Codiga <address@hidden> >Organization: University of Connecticut, Avery Point Campus >To: Steve Emmerson <address@hidden> >Subject: Re: 19990823: installing netCDF-3.4, linux >Keywords: 199908301437.IAA09536 In the above message, you wrote: > > Hi Steve > > I'm trying to install netCDF again, this time the 3.4 version. > > I ran > > ./configure > > and there were no apparent problems (config.log below). > > Then I ran > > make all >&! log & > > and this failed due to some errors. The logfile is appended below also. > In a previous email I sent you the output from 'uname' and 'env' on my > system. > > If there is any other info I can provide, let me know. Would you please send me the standard output and standard error from executing the configure script. > Otherwise, I'll wait for your suggestions on how to proceed. > > Thanks in advance. > Dan > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Codiga, Assistant Professor, Dept. of Marine Sciences > University of Connecticut, Avery Point Campus > Rm 214 Bldg 27, 1084 Shennecossett Rd, Groton, CT 06340-6097 > Phone/Fax: (860)405-9165/9153 Email: address@hidden > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Web: www.marinesciences.uconn.edu/codiga.html > And check out Coastal Studies: www.coastalst.uconn.edu > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > ------------------------------------------------------------------ > config.log ... > ----------------------------------------------------------------- > log > > make[1]: Entering directory `/usr/local/netcdf-3.4/src' > > Making `all' in directory /usr/local/netcdf-3.4/src/libsrc > > make[2]: Entering directory `/usr/local/netcdf-3.4/src/libsrc' ar cru > libnetcdf.a attr.o dim.o error.o libvers.o nc.o ncio.o ncx.o putget.o > string.o v1hpg.o v2i.o var.o ranlib libnetcdf.a make[2]: Leaving directory > `/usr/local/netcdf-3.4/src/libsrc' > > Returning to directory /usr/local/netcdf-3.4/src > > make[1]: Leaving directory `/usr/local/netcdf-3.4/src' > make[1]: Entering directory `/usr/local/netcdf-3.4/src' > > Making `all' in directory /usr/local/netcdf-3.4/src/fortran > > make[2]: Entering directory `/usr/local/netcdf-3.4/src/fortran' > cc -c -O -I../libsrc -DNDEBUG fort-attio.c > In file included from ncfortran.h:13, > from fort-attio.c:6: cfortran.h:151: #error "cfortran.h: > Can't find your environment among: - MIPS cc and f77 2.0. (e.g. Silicon > Graphics, DECstations, ...) - IBM AIX XL C and FORTRAN Compiler/6000 > Version 01.01.0000.0000 - VAX VMS CC 3.1 and FORTRAN 5.4 . - Alpha VMS > DEC C 1.3 and DEC FORTRAN 6.0. - Alpha OSF DEC C and DEC Fortran for > OSF/1 AXP Version 1.2 - Apollo DomainOS 10.2 (sys5.3) with f77 10.7 and cc > 6.7. > - CRAY - NEC SX-4 SUPER-UX - CONVEX - Sun > - PowerStation Fortran with Visual > C++ - HP9000s300/s700/s800 Latest test with: HP-UX A.08.07 A 9000/730 - > LynxOS: cc or gcc with f2c. > - VAXUltrix: vcc,cc or gcc with f2c. gcc or cc with f77. - f77 with > vcc works; but missing link magic for f77 I/O. - NO fort. None of gcc, cc > or vcc generate required names. - f2c : Use #define f2cFor tran, or cc > -Df2cFortran - NAG f90: Use #define NAGf90Fortran, or cc -DNAGf90Fortran - > Absoft UNIX F77: Use #define AbsoftUNIXFortran or cc -DAbsoftUNIXFortran" > make[2]: *** [fort-attio.o] Error 1 make[2]: Leaving directory > `/usr/local/netcdf-3.4/src/fortran' make[1]: *** [subdir_target] Error 1 > make[1]: Leaving directory `/usr/local/netcdf-3.4/src' make: *** > [fortran/all] Error 2 The above mess indicates that the netCDF installation procedure couldn't figure out what Fortan-calling-C convention to use (there are several, depending on what Fortran and C compilers you're using). What Fortran and C compilers are you using? -------- Steve Emmerson <http://www.unidata.ucar.edu>