970918: port of netCDF on Fujitsu VPP300

Gilles,

>Date: Fri, 19 Sep 1997 10:51:24 +22324452 
>From: Gilles Bourhis <address@hidden>
>Organization: France/IDRIS/Support Visualisation & Video
>To: Steve Emmerson <address@hidden>
>Subject: Re: 970918: port of netCDF on Fujitsu VPP300 
>Keywords: 199709181620.KAA00848

In the above message, you wrote:

> >     1.  The standard output from the command "uname -a".
> > 
> Here it is :
> UNIX_System_V shine0 4.1 ES 2 F300 UXP/V
> 
> >     2.  The standard output and error output from executing the
> >     configure script (*not* the file "config.log").  If you don't
> >     have this available, the go to the top-level netCDF source
> >     directory and execute the configure script while redirecting
> >     both standard output and standard error to a file.
> > 
> Here it is :
> loading cache ./config.cache
> checking for m4... (cached) m4
> checking user-defined C compiler "cc"
> checking C compiler... works
> checking how to make dependencies... false
> checking for CC... no
> checking for cxx... no
> checking for c++... no
> checking for g++... no
> checking for gcc... 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
> checking how to run the C preprocessor... (cached) cc -E
> checking user-defined FORTRAN compiler "frt"... 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 "integer*2" is C "short"... yes
> checking if FORTRAN "integer*2" is C "int"... 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
> checking for math library
> checking for -lc... (cached) no
> checking for -lm... (cached) yes
> checking for ar... (cached) ar
> checking for ranlib... (cached) :
> checking for stdlib.h... (cached) yes
> checking for sys/types.h... (cached) yes
> checking for strerror... (cached) yes
> checking for ftruncate... (cached) yes
> checking for st_blksize in struct stat... (cached) yes
> checking whether cross-compiling... (cached) no
> checking for IEEE floating point format... yes
> checking for ANSI C header files... (cached) yes
> checking for size_t... (cached) yes
> checking for off_t... (cached) yes
> checking for ssize_t... (cached) no
> checking for ptrdiff_t... (cached) yes
> checking for uchar... (cached) no
> checking whether char is unsigned... (cached) no
> checking whether byte ordering is bigendian... (cached) yes
> checking size of short... (cached) 2
> checking size of int... (cached) 4
> checking size of long... (cached) 4
> checking size of float... (cached) 4
> checking size of double... (cached) 8
> checking size of off_t... (cached) 4
> checking size of size_t... (cached) 4
> checking for catman... no
> checking for makewhatis... no
> checking for manual-page index command... 
> checking binary distribution directory... /home/ftp/pub/binary/dummy_system
> creating ./config.status
> creating macros.make
> udcreating fortran/nfconfig.inc
> creating libsrc/ncconfig.h
> libsrc/ncconfig.h is unchanged

The above looks very similar to Sun Fortran.  I'm surprised that using
the -DsunFortran option didn't work (that's what I would have tried).

I'll need more information.  Would you please do the following:

    1.  Go to the "fortran/" subdirectory.

    2.  Execute the command "make clean".

    3.  Execute the command "make".
        Redirect standard output and standard error to a file.
        Send me the file.
    
    4.  Execute the command "make test".
        Redirect standard output and standard error to a file.
        Send me the file.
        If an error occurred, then stop.

    5.  Go to the ../nf_test subdirectory.

    6.  Execute the command "make clean".

    7.  Execute the command "make".
        Redirect standard output and standard error to a file.
        Send me the file.
    
    8.  Execute the command "make test".
        Redirect standard output and standard error to a file.
        Send me the file.

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