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

Re: NEC SX-4 64 bit IEEE Netcdf

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: NEC SX-4 64 bit IEEE Netcdf
  • Date: Wed, 26 Nov 1997 16:29:39 -0700
> Yes. This is same as cray. i.e.
> NC_FLOAT corresponds to REAL
> NC_DOUBLE corresponds to DOUBLE PRECISION
> even though REAL and DOUBLE PRECISION are both 64 bits.

You are thinking of a 'classic' CRAY.
You have to be careful with thinking like that.
It turns out there is now a lot of variation, T3E vs T3D vs ...


> I took your advice & tried specifying argument float0 to C compiler.  This
did
> solve the problem.  Thanks.  I do not understand why I got some other mode by
> default.

Probably an environment variable.

> So now 'make' seems to work ok.  Then 'make test' runs two C tests ok, but
> then fails as follows in directory src/fortran:
>
> f77 -o ftest -float0 -ew  ftest.o ../libsrc/libnetcdf.a
> undefined                       first referenced
>  symbol                             in file
> nf_get_varm_int2_                   ftest.o
> nf_get_varm_int1_                   ftest.o
> nf_get_vars_int2_                   ftest.o
> nf_get_vars_int1_                   ftest.o
> nf_get_vara_int2_                   ftest.o
> nf_get_vara_int1_                   ftest.o
> nf_get_var1_int2_                   ftest.o
> nf_get_var1_int1_                   ftest.o
> nf_get_var_int2_                    ftest.o
> nf_get_var_int1_                    ftest.o
> nf_get_att_int2_                    ftest.o
> nf_get_att_int1_                    ftest.o
> nf_put_varm_int2_                   ftest.o
> nf_put_varm_int1_                   ftest.o
> nf_put_vars_int2_                   ftest.o
> nf_put_vars_int1_                   ftest.o
> nf_put_vara_int2_                   ftest.o
> nf_put_vara_int1_                   ftest.o
> nf_put_var1_int2_                   ftest.o
> nf_put_var1_int1_                   ftest.o
> nf_put_var_int2_                    ftest.o
> nf_put_var_int1_                    ftest.o
> nf_put_att_int2_                    ftest.o
> nf_put_att_int1_                    ftest.o
> ld fatal: symbol referencing errors. no output written to file ftest.
> f77 fatal : ld command error : 13
>
> I suspect these entry points are not needed, but they cause linkinf to fail.

ftest tests the version 2 compatibility interface (fort-v2compat.c).
I haven't seen this problem. I used FC=f90, not f77.

Is it possible that ftest.o or fort-v2compat.o were left over from a
previous build attempt?

Does 'make test' in nf_test/ fail as well?

-glenn