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

Re: 19990923: NETCDF Build on C90

George,

>Date: Wed, 22 Sep 1999 15:19:06 -0700
>From: "G_Shayne" <address@hidden>
>Organization: Microsoft Corporation
>To: "Steve Emmerson" <address@hidden>
>Subject: Re: 19990922: NETCDF Build on C90 
>Keywords: 199909212014.OAA06054

In the above message, you wrote:

> Attached are all of the log files.

I just notice a problem with the "make test" log file:

> Making `test' in directory /y/modas2/netcdf-3.4/src/libsrc
> 
>       cc -c -O3 -I.  -DNDEBUG t_nc.c
> FORCE: No action was taken.
>       ar cru   libnetcdf.a attr.o  dim.o  error.o  libvers.o  nc.o  ncio.o  
> ncx.o  putget.o  string.o  v1hpg.o  v2i.o  var.o
>       ranlib libnetcdf.a
> FORCE: No action was taken.
>       cc -o t_nc -O3  t_nc.o -L. -lnetcdf 
>       ./t_nc
> dimrename: IXX
> nc_close ret = 0
> 
> reopen id = 588063 for filename test.nc
> NC done
> GATTR VAR VATTR
> VATTR
> VATTR
> VATTR
> VATTR
> VATTR
> fill_seq indices       1 2 3  75.000000 != 2.718282
> Done
> got val = 3.250000
> got val = 0.000000
> got val = 2.718282
> got val = 82555
> got val = 97
> got NC_CHAR val = A (0x41) 
> got NC_CHAR val = B (0x42) 
> got NC_CHAR val = "The red death had long devastated the country."
> got val = A (0x41) 
> got val = B (0x42) 
> got val = "The red death had long devastated the country."
> got vals = 0.000000 ... 447.000000
> re nc_close ret = 0
>       cmp test.nc test_nc.sav
> *** Success ***
> 
> Returning to directory /y/modas2/netcdf-3.4/src
> 
> 
> Making `test' in directory /y/modas2/netcdf-3.4/src/nctest
> 
>       cc -c -O3 -I../libsrc  -DNDEBUG varget.c
>       cc -c -O3 -I../libsrc  -DNDEBUG vargetg.c
>       cc -c -O3 -I../libsrc  -DNDEBUG varput.c
>       cc -c -O3 -I../libsrc  -DNDEBUG varputg.c
>       cc -c -O3 -I../libsrc  -DNDEBUG vardef.c
>       cc -c -O3 -I../libsrc  -DNDEBUG vartests.c
>       cc -c -O3 -I../libsrc  -DNDEBUG vputget.c
>       cc -c -O3 -I../libsrc  -DNDEBUG vputgetg.c
>       cc -c -O3 -I../libsrc  -DNDEBUG driver.c
>       cc -c -O3 -I../libsrc  -DNDEBUG cdftests.c
>       cc -c -O3 -I../libsrc  -DNDEBUG dimtests.c
>       cc -c -O3 -I../libsrc  -DNDEBUG rec.c
>       cc -c -O3 -I../libsrc  -DNDEBUG atttests.c
>       cc -c -O3 -I../libsrc  -DNDEBUG misctest.c
>       cc -c -O3 -I../libsrc  -DNDEBUG add.c
>       cc -c -O3 -I../libsrc  -DNDEBUG error.c
>       cc -c -O3 -I../libsrc  -DNDEBUG emalloc.c
>       cc -c -O3 -I../libsrc  -DNDEBUG val.c
>       cc -c -O3 -I../libsrc  -DNDEBUG slabs.c
>       cc -o nctest -O3  varget.o vargetg.o varput.o varputg.o vardef.o 
> vartests.o  vputget.o vputgetg.o driver.o cdftests.o dimtests.o rec.o  
> atttests.o misctest.o add.o error.o emalloc.o val.o slabs.o -L../libsrc 
> -lnetcdf  
>       ./nctest

There should be a bunch of lines like the following at this point:

    *** Testing nccreate ...        ok ***
    *** Testing ncopen ...          ok ***
    *** Testing ncredef ...         ok ***
    *** Testing ncendef ...         ok ***
    *** Testing ncclose ...         ok ***
    ...

These lines are written by the "nctest" program to standard error.  The
fact that they don't appear in the log file indicates that the standard
error output of the "make test" wasn't redirected to the log file.  This
conclusion is supported later on in the log file by more missing lines
that should be there.

Because standard error wasn't redirected to the "make test" log file, it
is possible that I missed an error message that would indicate the cause
of your problem.  I suggest, therefore, that you rebuild the package
from scratch, ensuring that both standard error and standard output are
redirected to the log files at each step -- and then send me the log
files.  This entails executing steps 2 through 9 near the end of the
INSTALL file.

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