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.
>To: address@hidden >From: "rong" <address@hidden> >Subject: Re: 20010907: NetCDF HELP >Organization: Department of Atmospheric Sciences, Nanjing University(Nanjing >P.R.China) >Keywords: OSF1, F90 compiler error Hi, > I am a graduate student in the Department of Atmospheric Sciences, > Nanjing University(Nanjing P.R.China).I got the NetCDF package from > the home page: > > http://www.unidata.ucar.edu/packages/netcdf/index.html > > And put it on a OSF1 system.As I ran the "make",some problem > happened: > > /bin/f90 -c -O typeSizes.f90 > /bin/f90 -c -O netcdf.f90 > Severe: netcdf_text_variables.f90, line 57: Please report this error > along with > the circumstances in which it occurred in a Software Problem Report > localCount ( :numDims+1) = (/ len(values(1)), shape(values) /) > [ Aborting due to internal error. ] > > The environment was set by: > CC=/bin/cc > CPPFLAGS=-DNDEBUG > CFLAGS=-O > FC=/bin/f77 > FFLAGS=-O > F90=/bin/f90 > F90FLAGS=-O > CXX=/bin/cxx > CXXFLAGS=-O > > Why this problem happened?how could resolve it? On our OSF1 system with the same environment variable settings, the error does not occur: ... Making `all' in directory /tmp_mnt/scratch/russ/builds/dana-opt/src/f90 /bin/f90 -c -O typeSizes.f90 /bin/f90 -c -O netcdf.f90 ar cru ../libsrc/libnetcdf.a netcdf.o typeSizes.o ranlib ../libsrc/libnetcdf.a ... The error message "Severe: netcdf_text_variables.f90, line 57: ... " is from the f90 compiler rather than from the netCDF software, and the request to "Please report this error ..." is referring to reporting the compiler bug to the computer vendor. It's possible that we are using a later version of the f90 compiler that has a bug fix for this problem. The version we have is $ /bin/f90 -version Compaq Fortran V5.4-1283 Compaq Fortran Compiler V5.4-1283-46ABA One way to get around this problem is to specify that you don't want the Fortran90 interface built, by setting the environment variable F90='' before running the configure script (and after deleting the "config.cache" file). If you are only using netCDF because it's needed by some other program that is written in C or Fortran77, then the Fortran90 interface is unnecessary. Similarly, if you encounter errors compiling the C++ interface after skipping the f90 interface, you can also skip the C++ interface by setting the environment variable CXX='' before running the configure script. In the future, it would be better to send netCDF questions to address@hidden rather than to me, because then they will be forwarded to someone who can handle them even if I am away from my email. --Russ _____________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu