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.
------- Forwarded Message
Date: Wed, 04 Nov 1998 09:00:00 -0700
From: Russ Rew <address@hidden>
To: address@hidden (Wei Gong)
Subject: Re: 19981104: netCDF configure problem
>To: address@hidden
>cc: address@hidden
>From: address@hidden (Wei Gong)
>Organization: .
>Keywords: 199811032301.QAA00041
Hi Wei Gong,
> I try to install netcdf.tar.Z (Version 3.4) on my directory (SUN
> es6000). I did it as the following 7 steps:
>
> 1) uncompress netcdf.tar.Z
> 2) tar -xvf netcdf.tar
> 3) cd netcdf-3.4/src
> 4) configure
> 5) make
> 6) make test
> 7) make install
>
> After I did 4) configure, I found two errors in "config.log":
> --------------------------------------------------------------------
> configure:2084: c89 -o conftest -O -DNDEBUG conftest.c -lc 1>&5
> Undefined first referenced
> symbol in file
> tanh conftest.o
> ld: fatal: Symbol referencing errors. No output written to conftest
> --------------------------------------------------------------------
> configure:3052: c89 -c -O -DNDEBUG conftest.c 1>&5
> "configure", line 3047: undefined symbol: bogus
> "configure", line 3047: syntax error before or at: endian
> c89: acomp failed for conftest.c
> --------------------------------------------------------------------
>
> I do not know if the above errors will cause serious problems. How can
> I change the source code to eliminate these two errors. By the way, if
> 1)-7) are done, is the software finished installed?
The above errors are to be expected, and do not indicate any problem
with the netCDF installation. You are done installing netcdf if the
library, utilities, and documentation (in the lib/ and bin/ and man/
directories) are where you want them.
The errors in "config.log" are just a result of the configure script's
normal operation. As it says in the INSTALL document
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"). ...
- --Russ
_____________________________________________________________________
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu
------- End of Forwarded Message