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

Re: setting environment variables in compiler options

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: setting environment variables in compiler options
  • Date: Mon, 10 Jan 2005 14:23:03 -0700
>To: address@hidden
>From: Guy Williams <address@hidden>
>Subject: installing NetCDF for Absoft ProFortran 9.0 on Mac OS X
>Organization: Antarctic Climate and Ecosystems Co-operative Research Centre., 
>Australia
>Keywords: 200501050128.j051SJv2004103

Guy,

> I tried Ed's solution as well, both seem to work.
> 
> However, when I go back to my Absoft Tools GUI and
> try to BUILD my code, it successfully compiles and
> then trips over during linking with the same problem
> 
> ld: Undefined symbols:
> _NF_CLOSE
> ...
> 
> ./build/ozpom_NetCDF.o reference to undefined _NF_CLOSE
> ...
> 
> etc
> 
> i suspect i have to compile my code with the appropriate options to
> set the environment variables correctly.
> 
> could you tell me how to do this, as my initial attempts have failed
> through inexperience.

If you use Dierk Polzin's solution with the complex compiler options
and patch to cfortran.h, you will also have to compile any application
that uses netCDF with the same compiler option, as pointed out at 
http://my.unidata.ucar.edu/content/software/netcdf/other-builds.html#absoft-macosx

  WARNING: The above will cause the Fortran-callable routines in the
  netCDF library to be in lower-case symbols with trailing
  underscores; consequently, all packages that use the netCDF library
  will also have to be compiled using the options "-YEXT_NAMES=LCS
  -YEXT_SFX=_".

If you instead use Ed Hartnett's simpler solution, this should not be
necessary, although you may still have to link in utility functions
with "-lU77".  Make sure /Applications/Absoft/bin is in your PATH and
that you also have the environment variable
ABSOFT=/Applications/Absoft set.

--Russ