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

Re: 20051203: netCDF - FLAGS and NC_FILL_BYTE

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: 20051203: netCDF - FLAGS and NC_FILL_BYTE
  • Date: Fri, 09 Dec 2005 04:31:37 -0700
Bob Haxo <address@hidden> writes:

> Hi Ed ...
>
> Sorry for muddling the explanation...
>
> Setting the  F90FLAGS worked great with the makefile for 
> netcdf-3.6.0-p1/src/f90 files.
>
> It was the FFLAGS that did not work for F90. 
>
> The documentation states that if F90FLAGS is not defined, then the value of 
> FFLAGS will be used, i.e., the documentation seems to state that ...
>
>       if (F90FLAGS not set) then F90FLAGS=FFLAGS
>
> Well, the value of FFLAGS was apparently not being used for the value of 
> F90FLAGS when compiling the netcdf-3.6.0-p1/src/f90 files.  So I set the 
> F90FLAGS environment variable to the same value as the FFLAGS variable, and 
> all was fine.
>
> The Makefile in directory netcdf-3.6.0-p1/src/f90 includes ../macros.make 
> which defines the following:
>
> COMPILE.F90     = $(F90) -c $(F90FLAGS)
>
> there is no test for whether or not F90FLAGS is set, and then using the 
> FFLAGS 
> value in the event F90FLAGS is not set.
>
> --bob

OK, thanks for point this out.

The use of FFLAGS and F90FLAGS will be straightened out in release
4.0. Until then, use F90FLAGS.

Thanks!

Ed

-- 
Ed Hartnett  -- address@hidden