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.
Stefan, >Date: Tue, 04 Dec 2001 13:07:24 +0100 >From: Stefan Melber <address@hidden> >Organization: DLR Braunschweig >To: Steve Emmerson <address@hidden> >Subject: Re: 20011203: using NetCDF 3.4 on NEC-SX5: "not a NetCDF-file" >Keywords: 200111300742.fAU7gvN29708 The above message contained the following: > ok, let us find out the correct switches to compile netcdf on SX5. Currently i > am using 3.5.0 with the following switches: > > setenv CC "cc -Xa" > setenv CFLAGS "-h2" > setenv FC f90 > setenv F90 f90 > setenv FFLAGS "" > setenv CXX "" The "-Xa" option should probably have been in the CFLAGS or CPPFLAGS environment variable rather than the CC environment variable. What do the "-Xa" and "-h2" options do? > You will find the output of configure in the attachment. Is has some problems > with f90 and f77, both compilers are available ... dont know, what the problem > is. After configure, i make "make" and then "make test". The output of both > you will find in nec_com.o27470. > > Could you please have a look at the files ... i think, the c-part is ok, there > is only a problem with the fortran-part .... The file "configure.out" contained the following: checking user-defined Fortran-77 compiler "f90"... failed to compile test program The reason for the problem was in the file "config.log": configure:1383: checking user-defined Fortran-77 compiler "f90" configure:1389: f90 -c conftest.f conftest.f: f90 fatal : /usr/lib/f90com : Not enough space f90 fatal : /usr/lib/f90com command error : 12 You'll have to increase the amount of space available for the build and try again. Here are the steps: 1. Increase the amount of available space. 2. Go to the top-level source directory. 3. Perform steps 3 through 9 near the end of the file INSTALL.html. Regards, Steve Emmerson <http://www.unidata.ucar.edu>