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.
Caroline, ... > making `all' in directory /opt/udunits-1.12.4/src/lib > > make[1]: Entering directory `/opt/udunits-1.12.4/src/lib' > /usr/bin/gcc -c -O -fno-builtin -I../port/misc -I../port/cfortran > -DUT_DEFAULT_PATH='"/opt/udunits-1.12.4/etc/udunits.dat"' -DNDEBUG > -Df2cFortran utlib.c > Dans le fichier inclus � partir de utlib.c:29: > ../port/cfortran/cfortran.h:132:3: erreur: #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 g77Fortran, 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] Erreur 1 > make[1]: Leaving directory `/opt/udunits-1.12.4/src/lib' > make: *** [lib/all] Erreur 1 That is very strange. The header-file "cfortran.h" complains that one of the possible macros is not defined yet the compilation command very clearly defines the relevant macro "f2cFortran". What happens if you manually execute the command /usr/bin/gcc -c -O -fno-builtin -I../port/misc -I../port/cfortran \ -DUT_DEFAULT_PATH='"/opt/udunits-1.12.4/etc/udunits.dat"' -DNDEBUG -Df2cFortran utlib.c in the "lib" subdirectory? Regards, Steve Emmerson Ticket Details =================== Ticket ID: XZB-957825 Department: Support UDUNITS Priority: Normal Status: On Hold