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

Re: 961206: Problems installing netcdf

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: 961206: Problems installing netcdf
  • Date: Fri, 06 Dec 1996 15:51:56 -0700
>To: address@hidden
>From: address@hidden
>Subject: Problems installing netcdf 
>Organization: .
>Keywords: 199612061947.AA01686

Hi Jil,

> I removed the entire netcdf directory, untarred it again and started 
> fresh.  Here are the results.
> 
> #cd /usr/local/netcdf-2.4.3/src
> #configure
> # more config.log
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:1156: cc -E  conftest.c >/dev/null 2>conftest.out
> configure:1197: cc -E  conftest.c >/dev/null 2>conftest.out
> configure:1684: cc -c -O -Kpic  conftest.c 1>&5
> configure:1712: cc -o conftest -O   conftest.c  1>&5
> configure:1745: cc -o conftest -O   conftest.c  1>&5
> configure:1781: cc -o conftest -O   conftest.c  1>&5
> configure:1845: cc -o conftest -O   conftest.c  1>&5
> configure:1875: cc -o conftest -O   conftest.c  1>&5
> configure:1960: cc -o conftest -O   conftest.c  1>&5
> configure:2169: cc -o conftest -O   conftest.c  1>&5
> configure:2218: cc -c -O  conftest.c 1>&5
> "configure", line 2213: undefined struct/union member: x_getint
> "configure", line 2213: warning: improper pointer/integer combination: op 
> "="
> configure:2259: cc -c -O  conftest.c 1>&5
> configure:2292: cc -c -O  conftest.c 1>&5
> "configure", line 2287: warning: const is a keyword in ANSI C
> "configure", line 2287: undefined symbol: const
> "configure", line 2287: syntax error before or at: charset
> configure:2332: cc -c -O  -Dconst= conftest.c 1>&5
> "configure", line 2325: va_start: argument mismatch
> configure:2378: cc -o conftest -O  -Dconst=  conftest.c  1>&5
> configure:2450: cc -E  -Dconst= conftest.c >/dev/null 2>conftest.out
> configure:2484: cc -E  -Dconst= conftest.c >/dev/null 2>conftest.out
> configure:2510: cc -c -O  -Dconst= conftest.c 1>&5
> "configure", line 2502: identifier redeclared: malloc
>         current : function() returning pointer to struct {int a, int b}
>         previous: function() returning pointer to void : 
> "/usr/include/stdlib.h"
> , line 201
> # 

The output from running "configure" would be more useful in debugging
this problem than the "config.log" file.  Could you please do the
following from the netCDF netcdf-2.4.3/src/ directory?

 % make clean
 % rm config.cache
 % configure

and capture the output from this last command (how you do this depends
on which shell you're using).

> #make all >&! log &
> #Atail -f log
> 
> 
> 
> making `all' in directory /usr/local/netcdf-2.4.3/src/port
> 
> `all' is updated.
> 
> returning to directory /usr/local/netcdf-2.4.3/src
> 
> 
> making `all' in directory /usr/local/netcdf-2.4.3/src/xdr
> 
> 
> returning to directory /usr/local/netcdf-2.4.3/src
> 
> 
> making `all' in directory /usr/local/netcdf-2.4.3/src/libsrc
> 
> cc -c -Kpic -O -Dconst= array.c
> cc -c -Kpic -O -Dconst= attr.c
> cc -c -Kpic -O -Dconst= cdf.c
> cc -c -Kpic -O -Dconst= dim.c
> cc -c -Kpic -O -Dconst= file.c
> cc -c -Kpic -O -Dconst= iarray.c
> cc -c -Kpic -O -Dconst= error.c
> "error.c", line 130: va_start: argument mismatch
> "error.c", line 203: va_start: argument mismatch
> "error.c", line 150: warning: improper pointer/integer combination: op "="

The fact that these are being invoked with the compiler option
"-Dconst=" means you must be using something other than an ANSI C
compiler.  What C compiler are you using?  You can found out where it's
coming from by invoking "which cc", but the output of running
"configure" will also tell us.

Also I didn't save the output of your listing of environment variable
settings, but if you have CC set to some non standard C compiler, that
might explain the problem.  Could you also send your environment
variable settings again?  Thanks.

I just checked and netCDF 2.4.3 builds fine on our SunOS 5.5 system
using the /opt/SUNWspro/bin/cc ANSI C compiler.

--Russ

_____________________________________________________________________

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