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

951019: netCDF testing error

Dear Tong Li,

[You might not have received this message.]

> From: address@hidden (Magnetic Resonance Imaging/Benoit Dawant)
> Organization: Vanderbilt
> Keywords: 199510191602.AA15716 netCDF Fortran 

In the above message you wrote:
 
> I am trying to install netCDF on my system. When I used "make test " to
> test the software, I got following error message. It is related to the
> Fortran netCDF interface.  If I use only C language, can I just ignore
> the error?  Thank you for your help.
>                                                           Tong Li

Yes.  If you only intend to use the C API, then you can safely ignore
the error messages.

> *********************************************************************************************
...
making `test' in directory /ufs/users/mri/mcgill/netcdf-2.3.2/fortran
> make[1]: Entering directory `/ufs/users/mri/mcgill/netcdf-2.3.2/fortran'
> make[2]: Entering directory `/ufs/users/mri/mcgill/netcdf-2.3.2/fortran'
> ./fortc -L . -O sunos ftest.src > ftest.f
> f77 -c  ftest.f
> ftest.f:
>  MAIN ftest:
>       tncacpy:
>       tncadel:
>       tncagt:
>       tncapt:
>  BLOCK DATA:
>       tncddef:
>       tncinq:
>       tncredf:
>       tncvdef:
>       tncvgt:
>       tncvgt1:
>       tncvpt:
>       tncvpt1:
> ar rcuv ../libsrc/libnetcdf.a jackets.o
> f77 ftest.o -L../libsrc -lnetcdf -o ftest
> Undefined                     first referenced
>  symbol                           in file
> __cg92_used                         
> /opt/SUNWspro/SC2.0.1/cg92/libm.a(fp_class.o)
> ld: fatal: Symbol referencing errors. No output written to ftest
> make[2]: *** [ftest] Error 1
> make[2]: Leaving directory `/ufs/users/mri/mcgill/netcdf-2.3.2/fortran'
> /bin/sh: ./ftest: not found
> make[1]: *** [test] Error 1
> make[1]: Leaving directory `/ufs/users/mri/mcgill/netcdf-2.3.2/fortran'
> make: *** [fortran/test] Error 1

The SC2.3.2 development environment is out-of-date and we no longer have
access to it; consequently, we can't duplicate the problem.  I suggest
you upgrade to version SC3.0.1 as soon as possible to avoid future
problems.

--------
Steve Emmerson   <address@hidden>