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

970520: netcdf 3.3 with gcc

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: 970520: netcdf 3.3 with gcc
  • Date: Tue, 20 May 97 09:30:24 -0600
Kate,

>Date: Tue, 20 May 1997 11:26:56 -0400 (EDT) 
>From: Kate Hedstrom <address@hidden>
>Organization: Rutgers University
>To: address@hidden
>Subject: Re: 970520: netcdf 3.3 with gcc 
>Keywords: 199705171514.JAA09636

In the above message, you wrote:

> One more netcdf thing.  On the Solaris 2 machines we are getting tons
> of warnings of the form:
> 
> "/usr/local/include/netcdf.inc", line 912: Warning: local variable 
> "nf_get_varm_double" never used
> "/usr/local/include/netcdf.inc", line 928: Warning: local variable "nccre" 
> never used
> "/usr/local/include/netcdf.inc", line 929: Warning: local variable "ncopn" 
> never used
> 
> I can ignore them, but some of are users are put off by this, especially
> when a real error message is above all this stuff.  I got around this
> by adding lines like:
> 
>         external nf_get_varm_double
>         external nccre
>         external ncopn
> 
> Do you know of any reason why I shouldn't do this?

Because on another system you'll get warnings like "nf_get_varm_double
declared external but never called".

You can't win.  (You can't even get close.  ;-)

If your systems are mostly SunOS 4, then go ahead and add the EXTERNAL
statements.

--------
Steve Emmerson   <address@hidden>