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

NetCDF installation (IRIX 6.5)

Vladimir,

>Date: Sun, 19 Sep 2004 08:05:58 +0200
>From: "Vladimir Meerson" <address@hidden>
>Organization: Israel Meteorological Service
>To: "Steve Emmerson" <address@hidden>
>Subject: NetCDF installation (IRIX 6.5)
> Keywords: 200408111149.i7BBnPaW019090 netCDF IRIX

The above message contained the following:

> % uname -a
> IRIX64 smt-num 6.5 10151453 IP35
> 
> % more VERSION 
> 3.5.1
> 
> % env
> ...
> CPP=/bin/cc -64 -E
> CC=/bin/cc -64
> CPPFLAGS=-DNDEBUG
> CFLAGS=-O
> FPP=/bin/cc -64 -E
> FC=/bin/f90 -64
> FFLAGS=-O
> F90=/bin/f90 -64
> CXX=/bin/CC -64
> CXXFLAGS=-O
> 
> 
> Included files:
> 
> macros.make
> configure.log
> config.log
> make.log
> 
> Regards,
> Vladimir Meerson
> Israel Meteorological Service
> P.O.Box 25, Bet-Dagan ISRAEL
...

> creating cache ./config.cache
> checking for top-level source-directory
> /usr/people/vladimir/netcdf-3.5.1/src
> checking for m4 preprocessor
> checking for m4... m4
> checking m4 flags... -B10000
> checking C compiler "/bin/cc -64"... works
> checking how to make dependencies... cc -M
> checking for /bin/CC... /bin/CC -64
> checking C++ compiler "/bin/CC -64"... configure: warning: /bin/CC -64 =
> failed on standard C++ test program
> checking for -64... no
> configure: warning: Could not find working C++ compiler
> configure: warning: Setting CXX to the empty string
> configure: warning: The C++ interface will not be built

Do you need the C++ interface?

> checking how to run the C preprocessor... /bin/cc -64 -E
> checking user-defined Fortran-77 compiler "/bin/f90 -64"... works
> checking for Fortran preprocessor... /bin/cc -64 -E
> checking user-defined Fortran-90 compiler "/bin/f90 -64"... works
> checking for nm utility
> checking for nm... nm
> checking nm flags...=20
> checking for C-equivalent to Fortran routine "SUB"... sub_
> checking for Fortran "byte"... no
> checking for Fortran "integer*1"... yes
> checking for Fortran "integer*2"... yes
> checking if Fortran "integer*1" is C "signed char"... yes
> checking if Fortran "integer*1" is C "short"... no
> checking if Fortran "integer*1" is C "int"... no
> checking if Fortran "integer*1" 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"... integer*1
> checking for Fortran-equivalent to netCDF "short"... integer*2
> checking for math library
> checking for tanh in -lc... no
> checking for tanh in -lm... yes
> checking for ar utility
> checking for ar... ar
> checking ar flags... cru
> checking for nm utility
> checking for nm... (cached) nm
> checking nm flags...=20
> checking for ranlib... :
> checking for stdlib.h... no

I think the last line above is the first problem encountered by the
configure script because the header-file /usr/include/stdlib.h exists on
IRIX64 6.5 systems.  The corresponding lines in the file "config.status"
are the following:

    configure:2740: checking for stdlib.h
    configure:2750: /bin/cc -64 -E -DNDEBUG conftest.c >/dev/null =
    2>conftest.out
    configure: failed program was:
    #line 2745 "configure"
    #include "confdefs.h"
    #include <stdlib.h>

The file "conftest.out" is then checked by the configure-script for
error messages.

Let's execute that test manually.  Please send me the output from the
following commands:

    echo '#include <stdlib.h>' >conftest.c
    /bin/cc -64 -E -DNDEBUG conftest.c >/dev/null

Regards,
Steve Emmerson