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

Re: 20010815: netCDF installation errors

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: 20010815: netCDF installation errors
  • Date: Wed, 15 Aug 2001 16:32:30 -0600
>To: "address@hidden" <address@hidden>
>From: "Jim W Lee" <address@hidden>
>Subject: netCDF installation errors
>Organization: UCAR/Unidata
>Keywords: 200108152053.f7FKrd117949

Hi Jim,

> Hello!  I recently downloaded netCDF 3.5.0 from your website 
> (http://www.unidata.ucar.edu/packages/netcdf/), and attempted to 
> install it via the directions at 
> http://www.unidata.ucar.edu/packages/netcdf/INSTALL.html.  However, 
> when I ran ./configure, the config.log file that it generated had 
> several errors in it that I do not know how to fix.  I have included 
> the log file with this e-mail in the hopes that you may be able to 
> provide some assistance, or forward this to someone who could.  Thank 
> you for your time!

For the most part, you can ignore error messages in config.log,
because they're generated by the configure script in testing the
compiler environment; as it says in the INSTALL.html instructions:

  The configure script will also create the file "config.log", which
  will contain error messages from the utilities that the configure
  script uses in examining the attributes of your system. Because such
  an examination can result in errors, it is expected that "config.log"
  will contain error messages. Therefore, such messages do not
  necessarily indicate a problem (a better indicator would be failure of
  the subsequent "make"). One exception, however, is an error message in
  "config.log" that indicates that a compiler could not be started. This
  indicates a severe problem in your compilation environment -- one that
  you must fix.

So if there are error messages (not just warning messages) from the
subsequent "make" or something in the standard output of the configure
script indicating it couldn't find a compiler, feel free to send a
question about that to address@hidden, but I didn't see
anything in the config.log that you sent that indicated a problem ...

--Russ

_____________________________________________________________________

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