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.
Matt, >Date: Tue, 30 Dec 2003 09:26:34 +0800 >From: Matt Hipsey <address@hidden> >Organization: University of Western Australia >To: Steve Emmerson <address@hidden> >Subject: Re: 20031229: compiles OK but doesn't link on OS X The above message contained the following: > I suspected as much :). We played around with Absoft for a while on OSX > and got the netcdf OK, but couldn't get our code to run properly. > Hopefully, this XLF compiler may work. ... > without the -Df2cFortran I get the compile time error shown below ... > Making `all' in directory > /Users/hipsey/Documents/0A-WORK/02-CAEDYM/03-Code/2.0.1-1_devmac/ > netcdf-3.5.1-beta13/src/fortran > > cc -c -I../libsrc -DNDEBUG fort-attio.c > In file included from ncfortran.h:13, > from fort-attio.c:6: > cfortran.h:134: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 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 - > Absoft Pro Fortran: Use #define AbsoftProFortran - Portland Group > Fortran: Use #define pgiFortran" > make[2]: *** [fort-attio.o] Error 1 > make[1]: *** [subdir_target] Error 1 > make: *** [fortran/all] Error 2 OK. Try it again, but this time define the C macro IBMR2Fortran in the CPPFLAGS environment variable (it might not work, but it's worth a try): Remember to do a "make distclean" first. Send me the files "configure.log", "make.log", and (if you get that far) "test.log". Regards, Steve Emmerson