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.
Edward, >Date: Thu, 15 Mar 2001 15:24:03 -0700 (MST) >From: root <address@hidden> >Organization: US/Army >To: address@hidden >Subject: logs >Keywords: 200103131423.f2DENsL18476 The above message contained the following: > creating cache ./config.cache > checking for m4... m4 > checking for xlc... no > checking for c89... no > checking for acc... no > checking for cc... cc > checking C compiler... works > checking how to make dependencies... false > checking for CC... no > checking for cxx... no > checking for c++... c++ > checking C++ compiler "c++"... works > checking how to run the C preprocessor... cc -E > checking for f77... f77 > checking for Fortran .F compiler... > checking if Fortran compiler handles *.F files... yes > checking for C-equivalent to Fortran routine "SUB"... sub_ > checking for Fortran "byte"... yes > checking for Fortran "integer*2"... yes > checking if Fortran "byte" is C "signed char"... yes > checking if Fortran "byte" is C "short"... no > checking if Fortran "byte" is C "int"... no > checking if Fortran "byte" is C "long"... no > checking if Fortran "integer*2" is C "short"... yes > checking if Fortran "integer*2" is C "int"... no > checking if Fortran "integer*2" is C "long"... no > checking if Fortran "integer" is C "int"... yes > checking if Fortran "real" is C "float"... yes > checking if Fortran "doubleprecision" is C "double"... yes > checking for Fortran-equivalent to netCDF "byte"... byte > checking for Fortran-equivalent to netCDF "short"... integer*2 > checking for math library > checking for -lc... no > checking for -lm... yes > checking for ar... ar > checking for ranlib... ranlib > checking for stdlib.h... yes > checking for sys/types.h... yes > checking for strerror... yes > checking whether cross-compiling... no > checking for working ftruncate()... yes > checking for working alloca.h... yes > checking for alloca... yes > checking for st_blksize in struct stat... yes > checking for IEEE floating point format... yes > checking for ANSI C header files... yes > checking for size_t... yes > checking for off_t... yes > checking for ssize_t... yes > checking for ptrdiff_t... yes > checking for uchar... no > checking whether char is unsigned... no > checking whether byte ordering is bigendian... no > checking size of short... 2 > checking size of int... 4 > checking size of long... 4 > checking size of float... 4 > checking size of double... 8 > checking size of off_t... 4 > checking size of size_t... 4 > checking for manual-page index command... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > updating cache ./config.cache > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > creating libsrc/ncconfig > 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 f2cFortran, or cc -Df2cFortran \ > - NAG f90: Use #define NAGf90Fortran, or cc -DNAGf90Fortran \ > - Absoft UNIX F77: Use #define AbsoftUNIXFortran or cc > -DAbsoftUNIXFortran" The above error is probably caused by not having the C macro "f2cFortran" defined in the environment variable CPPFLAGS (the install file contains examples of this). Try the following: 1. Go to the to-level source directory. 2. Perform steps 3 through 5 near the end of the INSTALL file. 3. Ensure that the environment variable CPPFLAGS contains the string "-Df2cFortran". 4. Perform steps 6 through 9 near the end of the install file. > does this help sending from pine? Yes. Regards, Steve Emmerson <http://www.unidata.ucar.edu>