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.
George, Your Fortran compiler seems different from mine. In executing the configure script, I got the following excerpts: checking if Fortran compiler handles *.F files... yes ... checking if Fortran "real" is C "float"... yes checking if Fortran "doubleprecision" is C "double"... yes whereas you got the following: checking if Fortran compiler handles *.F files... no checking for Fortran preprocessor... cc -E ... checking if Fortran "doubleprecision" is C "double"... no checking if Fortran "doubleprecision" is C "float"... no The last two above are particularly troubling: they indicate that there is no C data type equivalent to a Fortran "doubleprecision". I've seen this before: it happens if the "-dp" option is omitted from the FFLAGS environment variable prior to executing the configure script from scratch (I just verified this on our C90). You said, however, that your FFLAGS environment variable contained the "-dp" option when you re-executed the configure script -- so there must be something else going on. I'm at a loss, however, to come up with what that something could be. Would you be willing to compile and execute some small test programs to uncover the problem? My version of the Fortran compiler is $ f90 -V Cray CF90 Version 3.1.0.0 09/22/99 10:51:33 What's yours? -------- Steve Emmerson <http://www.unidata.ucar.edu>