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

Re: 19980818: building netcdf on CRAY J90: ncvgt1 failure

George,

> To: address@hidden
> From: "George S. Lai" <address@hidden>
> Subject: building netcdf on CRAY J90
> Organization: NASA/GSFC
> Keywords: 199808181657.KAA22331

In the above message, you wrote:

>   I have been having difficulty in building netcdf on our CRAY
> J90 (sn9609 charney 9.2.0.05 roo.5 CRAY J90). I am wondering if
> you can help. I used the macros suggested in the INSTALL file,
> 
>     CC=/opt/ctl/bin/cc
>     CPPFLAGS=
>     CFLAGS= -O3
>     FC=/opt/ctl/bin/f90
>     FFLAGS="-g -F -dp"
>     CXX=/opt/ctl/bin/CC
>     CXXFLAGS=
> 
>   I copied libsrc/ncx_cray.c to libsrc/ncx.c before make. I tried 
> compiling with and without -DUSE_IEG on this module. I installed
> the patch "cray_patch" on libsrc/ffio.c which allows extra flags
> to pass into the assign command (I am not quite sure how this
> should be utilized, though). 
> 
>   Anyway, all different builds came into the same result -- everything
> built fine but the fortran binding didn't pass the test. The error 
> messages looked like 
> 
> ------------------------------------------------------------------
> *** Testing ncvgt1 ...
>  error in ncvgt1 double: 0.E+0  not close to 0.3333333333000006
> *** Testing ncvpt ...
> *** Testing ncopn, ncinq, ncdinq, ncvinq, ncanam, ncainq ...
>  error in ncvinq or ncvdef
> *** Testing ncvgt, ncvgtc ...
>  double error in ncvgt: 1,  0.E+0 .ne. 1.
>  double error in ncvgt: 2,  0.E+0 .ne. 2.
>  double error in ncvgt: 3,  R .ne. 3.

I don't see anything in the above that would cause this problem.

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

    1.  Send me the output from the command "uname -a".

    2.  Tell me what versions of the C and Fortran compilers you're
        using.

    3.  Go to the top-level, netCDF source directory.

    4.  Execute the command "make distclean".

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

    6.  Set your environment variables as before -- but don't use the 
        "-DUSE_IEG" option and remove the space in the "CFLAGS= -O3"
        setting (it's a typographical error).

    7.  Execute the configure script.  Redirect standard output and
        standard error to the file "configure.log".  Send me the file.

    8.  Send me the file "config.log".

    9.  Execute the command "make".  Redirect standard output and
        standard error to the file "make.log".  Send me the file.

    10. Execute the command "make test".  Redirect standard output and
        standard error to the file "test.log".  Send me the file.

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