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.
Katja, > To: address@hidden > From: Katja Stokley <address@hidden> > Subject: netcdf build error > Organization: IBM Global Services Federal > Keywords: 200002141752.KAA20917 netCDF IBM AIX configure In the above message, you wrote: > This is the netcdf which is part of the CCM_OMP benchmark distribution > package (http://www.scd.ucar.edu/css/benchmarks). Thanks for any > assistance. > > Katja > > > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> uname -a > AIX bf0915en 3 4 000048484C00 > > > VERSION: > 3.4 > > compilers: > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> echo $CC > xlc > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> which xlc > /usr/bin/xlc > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> echo $FC > xlf > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> which xlf > /usr/bin/xlf > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> echo $CXX > xlC > [bf]/home/blackforest/katjas/benchmarks/ccm_omp/netcdf> which xlC > /usr/bin/xlC You could save yourself some typing by just setting each environment variable to the absolute pathname of the associated utility, e.g. $ echo $CC /usr/bin/xlc > configure.log: > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "xlc" > checking C compiler... works > checking how to make dependencies... false > checking for xlC... xlC > checking C++ compiler "xlC"... works > checking how to run the C preprocessor... /lib/cpp > checking user-defined Fortran compiler "xlf"... 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"... yes > checking if Fortran "byte" is C "short"... no > checking if Fortran "byte" is C "int"... no > checking if Fortran "byte" is C "long"... no > checking if Fortran "integer*2" is C "short"... yes > checking if Fortran "integer*2" is C "int"... no > checking if Fortran "integer*2" is C "long"... no > 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"... 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... ranlib > checking for stdlib.h... yes > checking for sys/types.h... yes > checking for strerror... yes > checking whether cross-compiling... no > checking for working ftruncate()... yes > checking for working alloca.h... no > checking for alloca... yes > checking for st_blksize in struct stat... yes > 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... yes > 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... 4 > checking size of float... 4 > checking size of double... 8 > checking size of off_t... 4 > 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 > updating cache ./config.cache > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > creating libsrc/ncconfig.h > > config.log: > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:1020: xlc -c -g conftest.c 1>&5 > configure:1153: xlC -c conftest.C 1>&5 > configure:1220: xlc -E conftest.c >/dev/null 2>conftest.out > 1506-173 (W) Option lm is not valid. Enter xlc for list of valid options. > configure:1235: xlc -E -traditional-cpp conftest.c >/dev/null > 2>conftest.out > xlc: 1501-210 command option t contains an incorrect subargument > 1506-173 (W) Option lm is not valid. Enter xlc for list of valid options. > configure:1319: xlf -c -g conftest.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.f. > configure:1422: xlf -o conftest -g conftest.F > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.F. > configure:1463: xlf -c -g conftest.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.f. > configure:1498: xlf -c -g conftest.f > ** sub === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.f. > configure:1521: xlf -c -g conftest.f > ** sub === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.f. > configure:1555: xlc -c -g conftest.c > configure:1557: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1559: xlf -o conftest -g conftestf.o conftest.o > configure:1561: ./conftest > configure:1602: xlc -c -g conftest.c > configure:1604: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1606: xlf -o conftest -g conftestf.o conftest.o > configure:1608: ./conftest > configure:1649: xlc -c -g conftest.c > configure:1651: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1653: xlf -o conftest -g conftestf.o conftest.o > configure:1655: ./conftest > configure:1696: xlc -c -g conftest.c > configure:1698: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1700: xlf -o conftest -g conftestf.o conftest.o > configure:1702: ./conftest > configure:1747: xlc -c -g conftest.c > configure:1749: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1751: xlf -o conftest -g conftestf.o conftest.o > configure:1753: ./conftest > configure:1794: xlc -c -g conftest.c > configure:1796: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1798: xlf -o conftest -g conftestf.o conftest.o > configure:1800: ./conftest > configure:1841: xlc -c -g conftest.c > configure:1843: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1845: xlf -o conftest -g conftestf.o conftest.o > configure:1847: ./conftest > configure:1890: xlc -c -g conftest.c > configure:1892: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1894: xlf -o conftest -g conftestf.o conftest.o > configure:1896: ./conftest > configure:1937: xlc -c -g conftest.c > configure:1939: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1941: xlf -o conftest -g conftestf.o conftest.o > configure:1943: ./conftest > configure:1984: xlc -c -g conftest.c > configure:1986: xlf -g -c conftestf.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftestf.f. > configure:1988: xlf -o conftest -g conftestf.o conftest.o > configure:1990: ./conftest > configure:2023: xlf -c -g conftest.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.f. > configure:2044: xlf -c -g conftest.f > ** _main === End of Compilation 1 === > 1501-510 Compilation successful for file conftest.f. > configure:2084: xlc -o conftest -g conftest.c -lc 1>&5 > ld: 0711-317 ERROR: Undefined symbol: .tanh > ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more > information. > configure:2118: xlc -o conftest -g conftest.c -lm 1>&5 > configure:2213: /lib/cpp conftest.c >/dev/null 2>conftest.out > configure:2247: /lib/cpp conftest.c >/dev/null 2>conftest.out > configure:2297: xlc -o conftest -g conftest.c 1>&5 > configure:2331: xlc -o conftest -g conftest.c 1>&5 > configure:2398: xlc -o conftest -g conftest.c 1>&5 > configure:2428: xlc -o conftest -g conftest.c 1>&5 > "configure", line 2421.10: 1506-296 (S) #include file <alloca.h> not > found. > "configure", line 2424.9: 1506-196 (S) Initialization between types > "char*" and "int" is not allowed. > configure:2476: xlc -o conftest -g conftest.c 1>&5 > configure:2644: xlc -c -g conftest.c 1>&5 > configure:2702: xlc -o conftest -g conftest.c 1>&5 > configure:2731: /lib/cpp conftest.c >/dev/null 2>conftest.out > configure:2796: xlc -o conftest -g conftest.c 1>&5 > configure:3014: xlc -o conftest -g conftest.c 1>&5 > configure:3052: xlc -c -g conftest.c 1>&5 > "configure", line 3047.8: 1506-277 (S) Syntax error: possible missing ';' > or ','? > "configure", line 3047.2: 1506-045 (S) Undeclared identifier bogus. > configure:3098: xlc -o conftest -g conftest.c 1>&5 > configure:3136: xlc -o conftest -g conftest.c 1>&5 > configure:3170: xlc -o conftest -g conftest.c 1>&5 > configure:3204: xlc -o conftest -g conftest.c 1>&5 > configure:3238: xlc -o conftest -g conftest.c 1>&5 > configure:3272: xlc -o conftest -g conftest.c 1>&5 > configure:3310: xlc -o conftest -g conftest.c 1>&5 > configure:3348: xlc -o conftest -g conftest.c 1>&5 > > > -- > Katja Stokley > SP Applications Analyst - IBM Global Services Federal > Voice: 303.497.1212 address@hidden > Fax: 303.497.1804 address@hidden > I don't burn my candle at both ends; I only light it on very special > occasions. I didn't see any problem in the above. What happened when you executed the command "make". Regards, Steve Emmerson <http://www.unidata.ucar.edu>