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.
Hi,
OK, the output when running the configure script makes it look like
configure cannot run the Fortran compiler, as it should not get "no"
for these tests:
checking if Fortran "integer*2" is C "short"... no
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"... no
checking if Fortran "integer" is C "long"... no
checking if Fortran "real" is C "float"... no
checking if Fortran "real" is C "double"... no
checking if Fortran "doubleprecision" is C "double"... no
checking if Fortran "doubleprecision" is C "float"... no
See if there's some environment variable or maybe there's some setup
script you need to run before running the Fortran compiler, to make
sure it can find any runtime libraries that are needed. Please make
sure you can compile and run a simple Fortran program such as
program hw
print *, "hello, world"
end
before executing the configure script again. If any special options
are needed, you may need to set the FCFLAGS environment variable first
to make sure those flags are included on the compiler invocation line.
--Russ
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: OTY-454194
Department: Support netCDF
Priority: Normal
Status: Closed