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.
Liz, > From: address@hidden > Subject: cross-compiling...yes > Organization: CNC > Keywords: 199707181623.KAA05789 netCDF IRIX 64 In the above message, you wrote: > I am having a problem using configure for 64 bits. > Configure stops after checking for cross-compiling and for IEEE > format, and the environment does not get set up correctly for the > make, make test, and make install. > > I would appreciate your help... I have checked conftest.c, but > may also need to examine conftest.f to see why the syntax error > is occurring. I get the same warnings when compiling using -n32, > but do not see the same syntax error reported. > > Thanks for your help, Liz Hayes > > clear 208% uname -a > IRIX clear 6.2 03131015 IP22 > VERSION 3.3.1 > clear 218% vi config.log.64 > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:1017: /bin/cc -64 -c -O -woff 1110,1167 -DNDEBUG conftest.c 1>&5 > configure:1150: /bin/CC -64 -c -DNDEBUG conftest.C 1>&5 > configure:1217: /bin/cc -64 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:1316: /bin/f77 -64 -c -O conftest.f > configure:1415: /bin/f77 -64 -o conftest -O conftest.F > configure:1456: /bin/f77 -64 -c -O conftest.f > configure:1491: /bin/f77 -64 -c -O conftest.f > configure:1514: /bin/f77 -64 -c -O conftest.f > configure:1548: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1550: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1552: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected The above is a strange (and serious) error. It appears to indicate the the shell couldn't handle the following line in the configure script: if { (eval echo configure:1552: \"$doit\") 1>&5; (eval $doit) 2> &5; }; then What shell ran the configure script? Has it had any patches applied to it? > configure:1590: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1592: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1594: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1632: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1634: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1636: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1678: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1680: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1682: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1720: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1722: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1724: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1764: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1766: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1768: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1764: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1766: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1768: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1764: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1766: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1768: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1806: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1808: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1810: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1806: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1808: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1810: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1848: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1850: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1852: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1848: /bin/cc -64 -c -DNDEBUG -O -woff 1110,1167 conftest.c > configure:1850: /bin/f77 -64 -o conftest -O conftestf.f conftest.o > configure:1852: ./conftest > ./conftest: Syntax error at line 1: `(' unexpected > configure:1882: /bin/f77 -64 -c -O conftest.f > configure:1903: /bin/f77 -64 -c -O conftest.f > configure:1943: /bin/cc -64 -o conftest -O -woff 1110,1167 -DNDEBUG > conftest.c > - -lc 1>&5 > ld64: ERROR 33: Unresolved text symbol "tanh" -- 1st referenced by conftest.o. > ld64: INFO 60: Output file removed because of error. > configure:1977: /bin/cc -64 -o conftest -O -woff 1110,1167 -DNDEBUG > conftest.c > - -lm 1>&5 > configure:2072: /bin/cc -64 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2106: /bin/cc -64 -E -DNDEBUG conftest.c >/dev/null 2>conftest.out > configure:2156: /bin/cc -64 -o conftest -O -woff 1110,1167 -DNDEBUG > conftest.c > 1>&5 > configure:2204: /bin/cc -64 -o conftest -O -woff 1110,1167 -DNDEBUG > conftest.c > 1>&5 > configure:2238: /bin/cc -64 -c -O -woff 1110,1167 -DNDEBUG conftest.c 1>&5 > "configure", line 2234: warning(1171): expression has no effect > struct stat s; s.st_blksize; > ^ > > configure:2270: /bin/cc -64 -o conftest -O -woff 1110,1167 -DNDEBUG > conftest.c > 1>&5 > > > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "/bin/cc -64" > checking C compiler... works > checking how to make dependencies... cc -M > checking for /bin/CC... /bin/CC -64 > checking C++ compiler "/bin/CC -64"... works > checking how to run the C preprocessor... /bin/cc -64 -E > checking user-defined FORTRAN compiler "/bin/f77 -64"... 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"... yes > checking for FORTRAN "integer*2"... yes > checking if FORTRAN "byte" is C "signed char"... no > checking if FORTRAN "byte" is C "short"... no > checking if FORTRAN "byte" is C "int"... no > checking if FORTRAN "integer*2" is C "short"... no > checking if FORTRAN "integer*2" is C "int"... no > checking if FORTRAN "integer" is C "int"... no > checking if FORTRAN "integer" is C "long"... no > checking if FORTRAN "real" is C "float"... no > checking if FORTRAN "real" is C "double"... no > checking if FORTRAN "doubleprecision" is C "double"... no > checking if FORTRAN "doubleprecision" is C "float"... no > checking for FORTRAN-equivalent to netCDF "byte"... byte > 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... yes > checking for IEEE floating point format... > Argument expected > > environment variables: > CC=/bin/cc -64 > CFLAGS=-O -woff 1110,1167 > CPPFLAGS=-DNDEBUG > FC=/bin/f77 -64 > FFLAGS=-O > CXX=/bin/CC -64 > > I followed the following instructions from an archived support > e-mial. > ... > > > 5. Edit the file `configure'. Find the line that contains the string > > > `checking whether cross-compiling'. Insert the command `set -x' > > > before that line and the command `set +x' before the later line that > > > contains the string `checking size of int'. > > > > # If we cannot run a trivial program, we must be cross compiling. > > set -x > > echo $ac_n "checking whether cross-compiling""... $ac_c" 1>&6 > > if eval "test \"`echo '$''{'ac_cv_c_cross'+set}'`\" = set"; then > > > I assume the code gap at this point is because you didn't want to include > all the code. > > > set +x > > echo $ac_n "checking size of int""... $ac_c" 1>&6 > > if eval "test \"`echo '$''{'ac_cv_sizeof_int'+set}'`\" = set"; then > > > > > 6. Execute the configure script. Trap the output and send it to > > > me. > > % configure > > The output I obtained: > clear 236% !204 > ./configure --prefix=/usr/people/hayes/netcdf/netcdf-3.3.1/IRIX6_64 > > config.cross.comp > + echo checking whether cross-compiling... \c > + echo ${ac_cv_c_cross+set} > + eval test "${ac_cv_c_cross+set}" = set > + test = set > + test = yes > + cat > #line 2266 "configure" > #include "confdefs.h" > main(){return(0);} > + eval echo configure:2270: "${CC-cc} -o conftest $CFLAGS $CPPFLAGS $LDFLAGS > conftest.$ac_ext $LIBS 1>&5" > + echo configure:2270: /bin/cc -64 -o conftest -O -woff 1110,1167 -DNDEBUG > conftest.c 1>&5 > + test -s conftest > ac_cv_c_cross=yes > + echo yes > cross_compiling=yes > + echo checking for IEEE floating point format... \c > + test yes = yes > + : > + echo > + test = no > Argument expected > > > > ------- End of Forwarded Message -------- Steve Emmerson <http://www.unidata.ucar.edu>