[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 980306: compile problem

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.

  • Subject: Re: 980306: compile problem
  • Date: Fri, 06 Mar 1998 13:12:40 -0700
>To: address@hidden
>From: Brian Rizzo <address@hidden>
>Subject: compile problem
>Organization: Department of Environmental Sciences, University of Virginia
>Keywords: 199803061746.KAA28435

Hi Brian,

> I am new to netcdf.  Platform is PC under NT.  I have retreived netcdf files
> and unzipped them.  Also retreived NT make file routines and unzipped them
> into appropriate dir.  Using MS visual C ver. 5 to compile but will be using
> fortran in my actual work.  I ran nmake (C version) and was successful.  I
> then went into the fortran dir and did the same (nmake /f msoft.mak, again
> using C nmake command).  Again successful.  I then repeated the nmake with
> 'nmake / f msoft.mak test'.  process failed due to the following 
>    df /c /nologo /Zi /Od ftest.for
> the command 'df' is not recognized as an internal or external command.
> 
> If, as I assume, df is a unix command can you tell me what the equivalent
> command is under NT.  If you cannot help can point me to someone who could.

Good guess (there is an unrelated Unix command named "df" to report the
number of free disk blocks), but in this case "df" stands for Digital
Fortran, the name of a Fortran compiler designed for use with the MS
Visual C development environment (Microsoft no longer sells a Fortran
compiler).  In the msoft.mak file you are using, there is a macro
definition

  FOR=df

that specifies which Fortran compiler to use.  If you have a different
Fortran compiler, edit this definition to specify yours, then try
running "nmake /f msoft.mak test" again.

--Russ

_____________________________________________________________________

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu