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.
Ruben, > To: address@hidden > From: address@hidden > Organization: Technical University of Madrid/Computer Science School > Subject: netcdf-3.3.1 > Keywords: 199710021626.KAA16134 In the above message, you wrote: > Hi, I 'm a student at Technical University of Madrid. I'm working > with Prof. Roberto San Jose (address@hidden). > > After reading carefully the file INSTALL I have not been able to > install the netcdf-3.3.1. I send you the required outputs: > 1. The standard output of the command "uname -a". > > 2. The contents of the file VERSION, which is in the top-level > source directory. > > 3. The standard output and error output of the configure script > (step 4 above). > > 4. The absolute pathnames of all compilers (C, FORTRAN, C++) used > in the build process (use the type(1) or which(1) utility to > determine this). > > 5. The contents of the file "config.log", which is in the top-level > source directory. > > 6. The standard output and error output of the command "make" (step > 6 above). > > 7. The standard output and error output of the command "make test" > (step 7 above). > > > 1. sn1914 cadi 8.0.3.2 roo.1 CRAY Y-MP > 2. 3.3.1 > 3. standard output of the configure script: > > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "/bin/c89" > checking C compiler... works > checking how to make dependencies... false > checking how to run the C preprocessor... /bin/c89 -E > checking user-defined FORTRAN compiler "/opt/ctl/bin/f90"... works > checking for FORTRAN .F compiler... > checking if FORTRAN compiler handles *.F files... yes > checking for C-equivalent to FORTRAN routine "SUB"... SUB > checking for FORTRAN "byte"... no > checking for FORTRAN "integer*1"... yes > checking for FORTRAN "integer*2"... yes > checking if FORTRAN "integer*1" is C "signed char"... no > checking if FORTRAN "integer*1" is C "short"... yes > checking if FORTRAN "integer*1" is C "int"... yes > checking if FORTRAN "integer*2" is C "short"... yes > checking if FORTRAN "integer*2" is C "int"... yes > checking if FORTRAN "integer" is C "int"... yes > checking if FORTRAN "real" is C "float"... yes > checking if FORTRAN "doubleprecision" is C "double"... yes > checking for FORTRAN-equivalent to netCDF "byte"... integer*1 > checking for FORTRAN-equivalent to netCDF "short"... integer*2 > checking for math library > checking for -lc... yes > checking for ar... ar > checking for ranlib... : > checking for stdlib.h... yes > checking for sys/types.h... yes > checking for strerror... yes > checking for ftruncate... yes > checking for st_blksize in struct stat... yes > checking whether cross-compiling... no > checking for IEEE floating point format... no > checking for ANSI C header files... yes > checking for size_t... yes > checking for off_t... yes > checking for ssize_t... yes > checking for ptrdiff_t... yes > checking for uchar... yes > checking whether char is unsigned... yes > checking whether byte ordering is bigendian... yes > checking size of short... 8 > checking size of int... 8 > checking size of long... 8 > checking size of float... 8 > checking size of double... 8 > checking size of off_t... 8 > checking size of size_t... 8 > checking for catman... no > checking for makewhatis... no > checking for manual-page index command... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > updating cache ./config.cache > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > fortran/nfconfig.inc is unchanged > creating libsrc/ncconfig.h > libsrc/ncconfig.h is unchanged > > > error output of the configure script: > > configure: warning: Empty CXX variable > configure: warning: The C++ interface will not be built > > > 4. Pathnames of all compilers: > FC=/opt/ctl/bin/f90 > CC=/bin/c89 #the option CC=/opt/ctl/bin/c89 does not run > CXX= > > > 5. "config.log": > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:1017: /bin/c89 -c -O3 -DNDEBUG conftest.c 1>&5 > configure:1217: /bin/c89 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:1316: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1415: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F > configure:1415: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftest.F > configure:1456: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1491: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > cf90: Cray CF90 Version 2.x.x.x (f28a18t77) Thu Oct 2, 1997 17:05:05 > > byte value > ^ > cf90-724 f90: ERROR SUB, File = conftest.f, Line = 2, Column = 17 > Unknown statement. Expected assignment statement but found "EOS" instead > of " > =" or "=>". > > Cray CF90 Version 2.0.0.0 10/02/97 17:05:04 > cf90: COMPILE TIME 0.013000 SECONDS > cf90: MAXIMUM FIELD LENGTH 218665 DECIMAL WORDS > cf90: 3 SOURCE LINES > cf90: 1 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI > cf90: CODE: 0 WORDS, DATA: 0 WORDS > configure:1491: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1514: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1548: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1550: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1552: ./conftest > configure:1590: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1592: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1594: ./conftest > configure:1632: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1634: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1636: ./conftest > configure:1678: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1680: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1682: ./conftest > configure:1720: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1722: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1724: ./conftest > configure:1764: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1766: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1768: ./conftest > configure:1806: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1808: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1810: ./conftest > configure:1848: /bin/c89 -c -DNDEBUG -O3 conftest.c > configure:1850: /opt/ctl/bin/f90 -o conftest -O3 -i64 -dp -Wp-F conftestf.f > con > ftest.o > configure:1852: ./conftest > configure:1882: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > cf90: Cray CF90 Version 2.x.x.x (f28a18t77) Thu Oct 2, 1997 17:05:51 > > byte foo > ^ > cf90-724 f90: ERROR $MAIN, File = conftest.f, Line = 1, Column = 24 > Unknown statement. Expected assignment statement but found "EOS" instead > of " > =" or "=>". > > Cray CF90 Version 2.0.0.0 10/02/97 17:05:50 > cf90: COMPILE TIME 0.012000 SECONDS > cf90: MAXIMUM FIELD LENGTH 218665 DECIMAL WORDS > cf90: 2 SOURCE LINES > cf90: 1 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI > cf90: CODE: 0 WORDS, DATA: 0 WORDS > configure:1882: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1903: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1943: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c -lc 1>&5 > cc-252 c89: WARNING File = configure, Line = 1939 > Library function "tanh" is called with the wrong number of arguments. > > TOTAL WARNINGS DETECTED IN conftest.c: 1 > configure:2072: /bin/c89 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2106: /bin/c89 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2156: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2204: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2238: /bin/c89 -c -O3 -DNDEBUG conftest.c 1>&5 > cc-172 c89: WARNING File = configure, Line = 2234 > No code is generated for a superfluous expression. > > TOTAL WARNINGS DETECTED IN conftest.c: 1 > configure:2270: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2322: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > ^ > cf90-724 f90: ERROR $MAIN, File = conftest.f, Line = 1, Column = 24 > Unknown statement. Expected assignment statement but found "EOS" instead > of " > =" or "=>". > > Cray CF90 Version 2.0.0.0 10/02/97 17:05:50 > cf90: COMPILE TIME 0.012000 SECONDS > cf90: MAXIMUM FIELD LENGTH 218665 DECIMAL WORDS > cf90: 2 SOURCE LINES > cf90: 1 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI > cf90: CODE: 0 WORDS, DATA: 0 WORDS > configure:1882: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1903: /opt/ctl/bin/f90 -c -O3 -i64 -dp -Wp-F conftest.f > configure:1943: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c -lc 1>&5 > cc-252 c89: WARNING File = configure, Line = 1939 > Library function "tanh" is called with the wrong number of arguments. > > TOTAL WARNINGS DETECTED IN conftest.c: 1 > configure:2072: /bin/c89 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2106: /bin/c89 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2156: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2204: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2238: /bin/c89 -c -O3 -DNDEBUG conftest.c 1>&5 > cc-172 c89: WARNING File = configure, Line = 2234 > No code is generated for a superfluous expression. > > TOTAL WARNINGS DETECTED IN conftest.c: 1 > configure:2270: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2322: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c > 1configure:2322: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2351: /bin/c89 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2416: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2634: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2672: /bin/c89 -c -O3 -DNDEBUG conftest.c 1>&5 > cc-478 c89: ERROR File = configure, Line = 2667 > The identifier "bogus" is not declared. > > TOTAL ERRORS DETECTED IN conftest.c: 1 > configure:2718: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2756: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2790: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2824: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2858: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c > 1configure:2858: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2892: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2930: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > configure:2968: /bin/c89 -o conftest -O3 -DNDEBUG conftest.c 1>&5 > > > 6. standard output of "make": > > > Making `all' in directory > /u/upm/roberto/_librerias/libnetcdf/netcdf-3.3.1/src/l > ibsrc > > /bin/c89 -c -O3 -I. -DNDEBUG ncio.c > Make: "/bin/c89 -c -O3 -I. -DNDEBUG ncio.c": Error code 1 > Make: "cd libsrc && \ > echo "Making \`all' in directory `pwd`" && \ > echo "" && \ > make all || exit 1": Error code 1 > Make: "subdir=`echo libsrc/all | sed 's,/.*,,'`; \ > target=`echo libsrc/all | sed 's,.*/,,'`; \ > make SUBDIR=$subdir TGET=$target subdir_target": Error code 1 > > > > error output of "make": > > cc-526 c89: ERROR ncio.c, Line = 6, File = ./ffio.c, Line = 43 > The identifier "sb" is declared to have an incomplete type. > cc-421 c89: ERROR ncio.c, Line = 6, File = ./ffio.c, Line = 47 > The member name "st_oblksize" is not a member of the "struct" or "union". > > TOTAL ERRORS DETECTED IN ncio.c: 2 > > Stop. > > Stop. Hmm... The symbol "st_oblksize" appears to be undefined. I believe that it's defined in the C header-file <ffio.h>. Would you please check. Is it there? Is it conditional code that depends upon a certain C macro being defined? -------- Steve Emmerson <http://www.unidata.ucar.edu>