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.
Dear Steve,
Russ has passed your problem on to me (I'm the creator of the
installation procedure).
> Date: 30 May 1997 15:10:17 -0500
> From: "Steve Mauget" <address@hidden>
> To: "Russ Rew" <address@hidden>
> Subject: Re: 970529: OFFICE MEMO net
In the above message, you wrote:
> I went ahead and downloaded ver 3.3, and things seemed to going
> smoothly until the f90 compilations during "make". Seems that the
> NAG f90 compiler does not recognize the "*.F" file extensions
> in src/nf_test and routes them to the loader instead of the c
> pre-processor. The people at NAG claim that *.F are an exotic,
> non-standard extension,
The NAG people are correct in that the .F extension is used only by
exotic systems. Such systems include (but are not limited to) the
following:
System Compiler
------ --------
AIX xlf
BSD/OS fort77
HP-UX fort77
IRIX f77
IRIX64 f77
Linux fort77
OSF/1 f77
SunOS 4 f77
SunOS 5 f77
UNICOS f90
ULTRIX f77
These are, indeed, highly exotic systems. ;-)
Tell the NAG people to get off their butts and join the rest of the
world. :-)
In the meantime...
> so I'm currently trying to figure out how to
> turn *.F files into fortran source code using cpp. Maybe that was the
> same problem with the ver. 2.4.3 install.
The configure script should have automatically determined that your
FORTRAN compiler doesn't support .F files. I wonder what when wrong.
Would you please send me the standard output from your configure script
and also the file config.log.
--------
Steve Emmerson <address@hidden>