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.
Harvey, >Date: Fri, 5 Dec 1997 12:27:02 +1100 (EST) >From: Harvey DAVIES <address@hidden> >Organization: CSIRO Mathematical and Information Sciences >To: Steve Emmerson <address@hidden> >Subject: Re: NEC SX-4 64 bit IEEE Netcdf >Keywords: 199711262243.PAA12321 In the above message, you wrote: > Here is new configure.log using source from your harvey.tar.Z: > > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "cc -Xa" > checking C compiler... works > checking how to make dependencies... false > configure: warning: Empty CXX variable > configure: warning: The C++ interface will not be built > checking how to run the C preprocessor... cc -Xa -E > checking user-defined Fortran compiler "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"... no > checking for Fortran "integer(kind(1))"... yes > checking for Fortran "integer*2"... yes > checking if Fortran "integer(kind(1))" is C "signed char"... no > checking if Fortran "integer(kind(1))" is C "short"... no > checking if Fortran "integer(kind(1))" is C "int"... no > checking if Fortran "integer(kind(1))" is C "long"... yes > checking if Fortran "integer*2" is C "short"... no > checking if Fortran "integer*2" is C "int"... no > checking if Fortran "integer*2" is C "long"... yes > checking if Fortran "integer" is C "int"... no > checking if Fortran "integer" is C "long"... yes > checking if Fortran "real" is C "float"... no > checking if Fortran "real" is C "double"... yes > checking if Fortran "doubleprecision" is C "double"... yes > checking for Fortran-equivalent to netCDF "byte"... integer > checking for Fortran-equivalent to netCDF "short"... integer*2 > checking for math library > checking for -lc... no > checking for -lm... 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... yes > 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... no > checking whether char is unsigned... yes > checking whether byte ordering is bigendian... yes > checking size of short... 2 > checking size of int... 4 > checking size of long... 8 > checking size of float... 4 > checking size of double... 8 > checking size of off_t... 8 > checking size of size_t... 4 > checking for catman... catman > checking for manual-page index command... catman -w -M $(MANDIR) > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > cmp: EOF on ./config.cache > updating cache ./config.cache > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > creating libsrc/ncconfig.h Looks OK. > > Here is new config.log using source from your harvey.tar.Z: > > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:1017: cc -Xa -c -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:1217: cc -Xa -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:1316: f90 -c -float0 -ew conftest.f > conftest.f: > configure:1415: f90 -o conftest -float0 -ew conftest.F > /stmp/cshld.22412/ow28109_ppdir/i.conftest.F: > > f90: warn(82): i.conftest.F, line 4: Name "r" is not used. > f90: i.conftest.F, _MAIN: There is 1 warning. > configure:1456: f90 -c -float0 -ew conftest.f > conftest.f: > configure:1491: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: error(109): conftest.f, line 2: Unrecognizable statement. > f90: warn(83): conftest.f, line 3: Dummy argument "value" is not used. > f90: conftest.f, sub: There are 1 error and 1 warning. > f90 fatal : /usr/lib/f90com command error : 1 > configure:1491: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: error(430): conftest.f, line 2: Byte length specifier "1" is illegal. > f90: warn(83): conftest.f, line 3: Dummy argument "value" is not used. > f90: conftest.f, sub: There are 1 error and 1 warning. > f90 fatal : /usr/lib/f90com command error : 1 > configure:1491: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: warn(83): conftest.f, line 3: Dummy argument "value" is not used. > f90: conftest.f, sub: There is 1 warning. > configure:1514: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: warn(84): conftest.f, line 2: Length specification for INTEGER*2 or > LOGICAL*1 is ignored. > f90: warn(83): conftest.f, line 3: Dummy argument "value" is not used. > f90: conftest.f, sub: There are 2 warnings. > configure:1548: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1550: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1552: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1554: ./conftest > configure:1595: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1597: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1599: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1601: ./conftest > configure:1642: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1644: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1646: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1648: ./conftest > configure:1689: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1691: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1693: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1695: ./conftest > configure:1740: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1742: f90 -float0 -ew -c conftestf.f > conftestf.f: > > f90: warn(84): conftestf.f, line 1: Length specification for INTEGER*2 or > LOGICAL*1 is ignored. > f90: conftestf.f, _MAIN: There is 1 warning. > configure:1744: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1746: ./conftest > configure:1787: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1789: f90 -float0 -ew -c conftestf.f > conftestf.f: > > f90: warn(84): conftestf.f, line 1: Length specification for INTEGER*2 or > LOGICAL*1 is ignored. > f90: conftestf.f, _MAIN: There is 1 warning. > configure:1791: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1793: ./conftest > configure:1834: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1836: f90 -float0 -ew -c conftestf.f > conftestf.f: > > f90: warn(84): conftestf.f, line 1: Length specification for INTEGER*2 or > LOGICAL*1 is ignored. > f90: conftestf.f, _MAIN: There is 1 warning. > configure:1838: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1840: ./conftest > configure:1883: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1885: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1887: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1889: ./conftest > configure:1883: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1885: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1887: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1889: ./conftest > configure:1930: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1932: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1934: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1936: ./conftest > configure:1930: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1932: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1934: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1936: ./conftest > configure:1977: cc -Xa -c -DNDEBUG -hfloat0 conftest.c > configure:1979: f90 -float0 -ew -c conftestf.f > conftestf.f: > configure:1981: f90 -o conftest -float0 -ew conftestf.o conftest.o > configure:1983: ./conftest > configure:2016: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: error(109): conftest.f, line 1: Unrecognizable statement. > f90: conftest.f, _MAIN: There is 1 error. > f90 fatal : /usr/lib/f90com command error : 1 > configure:2016: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: error(430): conftest.f, line 1: Byte length specifier "1" is illegal. > f90: warn(82): conftest.f, line 2: Name "foo" is not used. > f90: conftest.f, _MAIN: There are 1 error and 1 warning. > f90 fatal : /usr/lib/f90com command error : 1 > configure:2016: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: warn(82): conftest.f, line 2: Name "foo" is not used. > f90: conftest.f, _MAIN: There is 1 warning. > configure:2037: f90 -c -float0 -ew conftest.f > conftest.f: > > f90: warn(84): conftest.f, line 1: Length specification for INTEGER*2 or > LOGICAL*1 is ignored. > f90: warn(82): conftest.f, line 2: Name "foo" is not used. > f90: conftest.f, _MAIN: There are 2 warnings. > configure:2077: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c -lc 1>&5 > undefined first referenced > symbol in file > tanh conftest.o > ld fatal: symbol referencing errors. no output written to file conftest. > configure:2111: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c -lm 1>&5 > configure:2206: cc -Xa -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2240: cc -Xa -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2290: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2338: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2372: cc -Xa -c -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2404: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2456: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2485: cc -Xa -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2550: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > "conftest.c", line 2544: vec inf: Unvectorized loop > configure:2768: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2806: cc -Xa -c -hfloat0 -DNDEBUG conftest.c 1>&5 > "configure", line 2801: undefined variable: bogus > "configure", line 2801: Syntax error before or at: endian > configure:2852: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2890: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2924: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2958: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:2992: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:3026: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:3064: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 > configure:3102: cc -Xa -o conftest -hfloat0 -DNDEBUG conftest.c 1>&5 I don't see any show stoppers. > Per says system has no specific argument for this purpose [making the > C compiler generate 8-byte "int"s]. In barbaric > desperation I tried: > CFLAGS='-hfloat0 -Dint=long' \ > However (as one example) /usr/include/stdio.h > contains line > short int _smode; /* stream mode */ > which made this fail. > > Per suggested using > typedef long int; > Can you suggest a way of specifying this typedef? In general, I'd expect such methods to fail if for no other reason than calls to the system runtime wouldn't know about 8-byte "int"s. This is going to take some work. I'll see what I can do. -------- Steve Emmerson <http://www.unidata.ucar.edu>