Re: 19981026: netCDF on T3D/E

Al,

>Date: Fri, 30 Oct 1998 14:42:48 -0500
>From: Al Bourgeois <address@hidden>
>Organization: Lockheed Martin
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19981026: netCDF on T3D/E
>Keywords: 199810292226.PAA24396

In the above message, you wrote:

> >     1.  Do you need the Fortran interface?

> Yes. All of the calls to netCDF routines are made from FORTRAN routines.

Then we'd better get it working.

> >     2.  If so, then
> > 
> >         A.  What are the Fortran types that are equivalent to the
> >             following C types:

> Should be:
>                   C types           FORTRAN
> 
> >                 signed char       Not sure there is one. Perhaps BYTE.
> >                 short             INTEGER*2
> >                 int               INTEGER*4
> >                 long              INTEGER*8
> >                 float             REAL*4
> >                 double            REAL*8, or just REAL

This seems reasonable (and doable).

> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:1020: cc -c -O -DNDEBUG conftest.c 1>&5
> configure:1319: cf77 -c -g -dp conftest.f
> configure:1422: cf77 -o conftest -g -dp conftest.F  
> 1$MAIN   PAGE 1      CRAY FORTRAN CFT77 6.2.1.4  11/28/95 07:07:29         
> 10/29/98 10:40:11      PAGE 1
>   
>       6      6.               real r(J,N)
>                                    ^
>  cft77-417 cf77: ERROR $MAIN, Line = 6, File = /tmp/jtmp.003741a/conftest.f, 
> Line = 6
>    Adjustable arrays are allowed only in function and subroutine program 
> units.
>  cft77-42 cf77: Cray CFT77_M Version 6.2.1.4  (281382) 10/29/98 10:40:11
>  cft77-2  cf77: COMPILE TIME     .013 SECONDS
>  cft77-6  cf77: MAXIMUM FIELD LENGTH   439091 DECIMAL WORDS
>  cft77-3  cf77: 7 SOURCE LINES
>  cft77-4  cf77: 1 ERROR, 0 WARNING, 0 CAUTION, 0 COMMENT, 0 NOTE, 0 ANSI
>  cft77-5  cf77: CODE: 0 WORDS, DATA: 0 WORDS
> configure:1463: cf77 -c -g -dp conftest.f
> configure:1498: cf77 -c -g -dp conftest.f
> 1SUB   PAGE 1      CRAY FORTRAN CFT77 6.2.1.4  11/28/95 07:07:29         
> 10/29/98 10:40:13      PAGE 1
>   
>       2      2.       byte value
>                       ^
>  cft77-318 cf77: ERROR SUB, Line = 2, File = conftest.f, Line = 2
>    "BYTEVALUE" is not a valid statement.
>       3      3.       end
>                      ^
>  cft77-323 cf77: ERROR SUB, Line = 3, File = conftest.f, Line = 3
>    Input symbol is "end of statement", but "= or (" was expected.
>  cft77-42 cf77: Cray CFT77_M Version 6.2.1.4  (281382) 10/29/98 10:40:13
>  cft77-2  cf77: COMPILE TIME     .016 SECONDS
>  cft77-6  cf77: MAXIMUM FIELD LENGTH   439088 DECIMAL WORDS
>  cft77-3  cf77: 3 SOURCE LINES
>  cft77-4  cf77: 2 ERROR, 0 WARNING, 0 CAUTION, 0 COMMENT, 0 NOTE, 0 ANSI
>  cft77-5  cf77: CODE: 0 WORDS, DATA: 0 WORDS
> configure:1498: cf77 -c -g -dp conftest.f
> configure:1521: cf77 -c -g -dp conftest.f
> configure:1555: cc -c -DNDEBUG -O conftest.c
> configure:1557: cf77 -g -dp -c conftestf.f
> configure:1559: cf77 -o conftest -g -dp  conftestf.o conftest.o 
> configure:1561: ./conftest
> mppexec: Invalid number of PEs specifed (NPES=0).

Hmmm...  There are a lot of "Invalid number of PEs specifed (NPES=0)"
messages in this file.   I suspect that the test programs that the
configure script creates aren't being executed because of this and that,
consequently, the configure script is interpreting their failure as a
negative test result.

Could it be that your environment needs to be modified prior to
executing the configure script (by setting the MPP_NPES environment
variable to "1", for example)?

Try the following:

    1.  Go to the top-level source directory.

    2.  Execute the command "make distclean".

    3.  Remove the file "config.cache" if it exists.

    4.  Set your environment variables as before.

    5.  Set the environment variable MPP_NPES (or equivalent) to 1.

    6.  Execute the configure script.  Redirect standard output and
        standard error to the file "configure.log".  If an error message
        occurs in the output, then stop and send me the files
        "configure.log" and "config.log".

    7.  Execute the command "make".  Redirect standard output and
        standard error to the file "make.log".  If an error occurs, then
        stop and send me the files "make.log", "configure.log", and
        "config.log".

    8.  Execute the command "make test".  Redirect standard output and
        standard error to the file "test.log".  If an error occurs,
        then stop and send me the files "test.log", "make.log",
        "configure.log", and "config.log".

    9.  Execute the command "make install".  Redirect standard output and
        standard error to the file "install.log".  If an error occurs,
        then stop and send me the file "install.log".

    10. Execute the command "make clean".

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