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

Re: 980415: problems building netCDF 3.4 under HPUX 10.20

Gregg,

>Date: Wed, 15 Apr 1998 13:45:56 -0600 
>From: Gregg Phillips <address@hidden>
>Organization: NOAA/ERL/FSL/MD Boulder, CO 
>To: Steve Emmerson <address@hidden>
>Subject: Re: 980415: problems building netCDF 3.4 under HPUX 10.20 
>Keywords: 199804151618.KAA15463 netCDF 3.4 build

In the above message, you wrote:

> It appears as though we have the same version of the C compiler:
> 
> B3898AA_APZ                   B.10.20.02     HP C/ANSI C Developer's Bundle 
> for
> HP-UX 10.20 (S700)
> 
> I am including the output from configure. Please note I have to modify the
> macros.make file to set the flags you recommend.

That definitely should not have been necessary and may cause problems.

> 
> Thanks for your help,
> 
> Gregg.
> 
> creating cache ./config.cache
> checking for m4... m4
> checking for xlc... no
> checking for c89... c89
> checking C compiler... works
> checking how to make dependencies... false
> checking for CC... CC
> checking C++ compiler "CC"... works
> checking how to run the C preprocessor... c89 -E
> checking for fort77... no
> checking for Fortran .F compiler... 
> checking for Fortran preprocessor... c89 -E
> checking for math library
> checking for -lc... no
> checking for -lm... yes
> checking for ar... ar
> checking for ranlib... ranlib
> checking for stdlib.h... yes
> checking for sys/types.h... yes
> checking for strerror... yes
> checking whether cross-compiling... no
> checking for working ftruncate()... no
> checking for working alloca.h... yes
> checking for alloca... yes
> checking for st_blksize in struct stat... no
> checking for IEEE floating point format... yes
> checking for ANSI C header files... yes
> checking for size_t... yes
> checking for off_t... no
> checking for ssize_t... no
> checking for ptrdiff_t... yes
> checking for uchar... no
> checking whether char is unsigned... no
> checking whether byte ordering is bigendian... yes
> checking size of short... 2
> checking size of int... 4
> checking size of long... 4
> checking size of float... 4
> checking size of double... 8
> checking size of off_t... 4
> checking size of size_t... 4
> checking for manual-page index command... 
> checking binary distribution directory... /home/ftp/pub/binary/dummy_system
> updating cache ./config.cache
> creating ./config.status
> creating macros.make
> udcreating fortran/nfconfig.inc
> creating libsrc/ncconfig.h

The above configure script output doesn't look like ours -- of which the
first part is the following:

    creating cache ./config.cache
    checking for m4... m4
    checking user-defined C compiler "/bin/c89"
    checking C compiler... works
    checking how to make dependencies... cc -M
    checking for g++... g++
    checking C++ compiler "g++"... works
    checking how to run the C preprocessor... /bin/c89 -E
    checking user-defined Fortran compiler "/bin/f77"... works
    checking for Fortran .F compiler... 
    checking if Fortran compiler handles *.F files... yes
    checking for C-equivalent to Fortran routine "SUB"... sub_
    checking for Fortran "byte"... yes
    checking for Fortran "integer*2"... yes
    checking if Fortran "byte" is C "signed char"... yes
    checking if Fortran "byte" is C "short"... no
    checking if Fortran "byte" is C "int"... no
    checking if Fortran "byte" is C "long"... no
    checking if Fortran "integer*2" is C "short"... yes
    checking if Fortran "integer*2" is C "int"... no
    checking if Fortran "integer*2" is C "long"... no
    checking if Fortran "integer" is C "int"... yes
    checking if Fortran "real" is C "float"... yes
    checking if Fortran "doubleprecision" is C "double"... yes
    checking for Fortran-equivalent to netCDF "byte"... byte
    checking for Fortran-equivalent to netCDF "short"... integer*2
    ...

Given identical operating systems, environment variable settings, and
compilation utilities, there should be no discrepancies in the output
from the configure script.

Does the VERSION file in your distribution contain the string "3.4"?

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