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

20040910: Mac OS X 10.3.4, NetCDF 3.5.1

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: 20040910: Mac OS X 10.3.4, NetCDF 3.5.1
  • Date: Mon, 13 Sep 2004 14:36:32 -0600
Russ & Cara-Lyn,

>Date: Fri, 10 Sep 2004 16:36:21 -0600
>From: Russ Rew <address@hidden>
>Organization: UCAR Unidata Program
>To: Cara-Lyn Lappen <address@hidden>
>Subject: Re: 20040910: Mac OS X 10.3.4, NetCDF 3.5.1 
>Keywords: 200409101811.i8AIBvdL027131

The above message contained the following:

> Our netCDF Fortran interface expert, Steve Emmerson, is out until next
> week, but I'll forward this to him in case he knows a better way to
> handle this than modifying the netCDF source.

I reviewed this thread in our netCDF support-email archive and
something doesn't make sense.  The original problem was that the CAM
package required upper-case symbols (e.g., "_NF_CLOSE_") but that the
Fortran-callable symbols in the netCDF library were lower-case (e.g.,
"_nf_close_").

The "cfortran.h" file, however, does generate upper-case symbols if the
C macro "AbsoftProFortran" is defined.

Could it be that the C macro "AbsoftProFortran" wasn't defined in
the CPPFLAGS environment variable when the configure(1) script was
originally executed?

Regards,
Steve Emmerson