971111: configure scripts thinks it's cross_compiling

Ladean,

>Date: Tue, 11 Nov 97 12:49:58 -0700 
>From: "Ladean R. McKittrick" <ladeanm@cyclops>
>Organization: University of Montana
>To: Steve Emmerson <address@hidden>
>Subject: Re: 971111: configure scripts thinks it's cross_compiling 
>Keywords: 199711110230.TAA05658

In the above message, you wrote:

> >   5.  Send me the files "configure.log" and "config.log".
> 
> ********************************************************************************config.log
> *******************************************************************************
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:1156: c89 -E  -D_ALL_SOURCE conftest.c >/dev/null 2>conftest.out
> configure:1197: c89 -E  -D_ALL_SOURCE conftest.c >/dev/null 2>conftest.out
> configure:1663: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:1696: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:1732: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:1796: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:1826: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:1911: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:2120: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:2193: c89 -c -O  -D_ALL_SOURCE conftest.c 1>&5
> configure:2226: c89 -c -O  -D_ALL_SOURCE conftest.c 1>&5
> "configure", line 2221.51: 1506-359 (W) Automatic variable x contains a const 
> me
> mber and is not initialized.  Zero is being assumed.
> configure:2266: c89 -c -O  -D_ALL_SOURCE conftest.c 1>&5
> configure:2312: c89 -o conftest -O  -D_ALL_SOURCE  conftest.c  1>&5
> configure:2384: c89 -E  -D_ALL_SOURCE conftest.c >/dev/null 2>conftest.out
> configure:2418: c89 -E  -D_ALL_SOURCE conftest.c >/dev/null 2>conftest.out
> configure:2444: c89 -c -O  -D_ALL_SOURCE conftest.c 1>&5
> "configure", line 2436.51: 1506-343 (S) Redeclaration of malloc differs from 
> pre
> vious declaration on line 169 of "/usr/include/stdlib.h".
> "configure", line 2436.51: 1506-050 (I) Return type "struct {...}*" in 
> redeclara
> tion is not compatible with the previous return type "void*".
> 
> ********************************************************************************configure.log
> ********************************************************************************creating
>   
> cache ./config.cache
> checking for catman... no
> checking for fill-value usage... new usage
> checking the installation prefix...  
> /home/wings/u0/FEM_etc/SEAMS/ACCESS/netcdf/netcdf_2.4.2
> checking the installation exec-prefix...  
> /home/wings/u0/FEM_etc/SEAMS/ACCESS/netcdf/netcdf_2.4.2
> checking for c89... c89
> checking type of operating system... aix
> checking type of machine... rs6000
> checking for ranlib... ranlib
> checking how to run the C preprocessor... c89 -E
> checking the C preprocessor... works
> checking for f77... f77
> checking for C++ compiler...
> checking for yacc... yacc
> checking for neqn... neqn
> checking for tbl... tbl
> checking for ar... ar
> checking for makeinfo... no
> checking for tar flags... -chf
> checking for dependency generation mechanism... c89 -M
> checking whether cross-compiling... no

Interesting.  The configure script doesn't think it's cross-compiling.
Apparently, the problem has gone away.

> checking size of int... 4
> checking size of long... 4
> checking type of nclong... long
> checking endianess... big endian
> checking type of netlong... long
> checking type of internal netlong... long
> checking for XDR header-file... -I/usr/include/rpc
> checking for XDR library...
> checking for xdr_long in default library... yes
> checking XDR implementation... ok
> checking type pointed to by inline XDR function... netlong
> checking XDR library for xdr_getint()... checking which XDR module to use...  
> xdrposix
> checking for function prototype... yes
> checking for working const... yes
> checking for variadic function support... yes
> checking for strerror... yes
> checking compiler options for IEEE arithmetic...
> checking for size of block buffer... 8192
> checking for float.h... yes
> checking for stdlib.h... yes
> checking C header file <stdlib.h> for function malloc()... declared
> checking for package version... 2.4

Why are you using version 2.4 of the netCDF package when the latest
release is version 3.3.1?

> checking binary distribution directory... /home/ftp/pub/binary/rs6000-aix
> updating cache ./config.cache
> creating ./config.status
> creating Makefile
> creating xdr/Makefile
> creating libsrc/Makefile
> creating fortran/Makefile
> creating cxx/Makefile
> creating ncgen/Makefile
> creating ncdump/Makefile
> creating nctest/Makefile
> creating doc/Makefile
> creating port/master.mk
> creating port/Makefile
> creating libsrc/local_nc.h
> libsrc/local_nc.h is unchanged
> expanding `include's in file `Makefile'
> expanding `include's in file `xdr/Makefile'
> expanding `include's in file `libsrc/Makefile'
> expanding `include's in file `fortran/Makefile'
> expanding `include's in file `cxx/Makefile'
> expanding `include's in file `ncgen/Makefile'
> expanding `include's in file `ncdump/Makefile'
> expanding `include's in file `nctest/Makefile'
> expanding `include's in file `doc/Makefile'
> expanding `include's in file `port/master.mk'
> expanding `include's in file `port/Makefile'
> ********************************************************************************

The above looks OK.  You can either go on and build and install it
(following the instructions in the INSTALL file) or you can dump it and
install version 3.3.1 instead (which we recommend -- version 2.4 isn't
supported anymore).

--------
Steve Emmerson   <http://www.unidata.ucar.edu>