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.
Gary, > To: <address@hidden> > From: "Liu,Gary [Ontario]" <address@hidden> > Subject: Installation Problem > Organization: UCAR/Unidata > Keywords: 200502241712.j1OHCMv2027085 The above message contained the following: > I had encounter problems while installing udunits-1.12.4 > > The attached file is log of the 'configure' and 'make' process > > <<log>>=20 > Thanks > > Gary Liu The problem you encountered: making `all' in directory /home/gary/udunits-1.12.4/src/lib make[1]: Entering directory `/home/gary/udunits-1.12.4/src/lib' c89 -c -g -O2 -I../port/misc -I../port/cfortran -DUT_DEFAULT_PATH='"/home/gary/udunits-1.12.4/etc/udunits.dat"' utlib.c In file included from utlib.c:29: ../port/cfortran/cfortran.h:132:3: #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 DE C 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 - Absoft Pro Fortran: Use #define AbsoftProFortran - Portland Group Fortran: Use #define pgiFortran" make[1]: *** [utlib.o] Error 1 make[1]: Leaving directory `/home/gary/udunits-1.12.4/src/lib' make: *** [lib/all] Error 1 means that the C compiler didn't know what Fortran calling-conventions to use to build the Fortran interface. The C compiler is given this information by the definition of an appropriate C macro in the CPPFLAGS environment variable prior to the execution of the configure(1) script. Examples of such definitions are in the file INSTALL. Please try the following: 1. Go to the top-level source-directory 2. Perform steps 3 through 5, described near the end of the file INSTALL. 3. Ensure that the environment variable CPPFLAGS contains the string "-Df2cFortran". 4. Perform steps 6 through 9, described near the end of the file INSTALL. Please let me know if this helps. Regards, Steve Emmerson