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.
Harsh, >Date: Tue, 31 Aug 1999 08:47:37 -0700 >From: Harsh Anand <address@hidden> >Organization: LBNL/NERSC >To: Steve Emmerson <address@hidden> >Subject: Re: 19990830: netcdf-3.4 installation make fails on IBM RS/6000 >Keywords: 199908302133.PAA20130 In the above message, you wrote: > Here are the environment variables I set before I run 'configure': > > setenv CC xlc > setenv CPPFLAGS -DNDEBUG > setenv CFLAGS "-O -D_XOPEN_SOURCE" > setenv FC xlf > setenv FFLAGS -O > setenv CXX KCC > setenv LIBS "-L /lib -lm" > > Here is the configure.log listing. Note this time: > > checking for IEEE floating point format... yes > > ******************************************** > > more 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 KCC... KCC > checking C++ compiler "KCC"... 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... 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... Hello > Hello > 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 Good! > 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 > > ******************************************************************* > FYI -- make fails. Bad! > *********************************************************************** > >more make-log > make[1]: Entering directory `/usr/common/usg/netcdf/3.4/src' > > Making `all' in directory /usr/common/usg/netcdf/3.4/src/libsrc > > make[2]: Entering directory `/usr/common/usg/netcdf/3.4/src/libsrc' > xlc -c -O -D_XOPEN_SOURCE -I. -DNDEBUG attr.c > "ncx.h", line 229.37: 1506-046 (S) Syntax error. > "ncx.h", line 229.46: 1506-046 (S) Syntax error. > "ncx.h", line 244.43: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 260.35: 1506-046 (S) Syntax error. > "ncx.h", line 260.44: 1506-046 (S) Syntax error. > "ncx.h", line 275.41: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 291.37: 1506-046 (S) Syntax error. > "ncx.h", line 291.46: 1506-046 (S) Syntax error. > "ncx.h", line 306.43: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 322.38: 1506-046 (S) Syntax error. > "ncx.h", line 322.47: 1506-046 (S) Syntax error. > "ncx.h", line 337.44: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 414.55: 1506-046 (S) Syntax error. > "ncx.h", line 414.64: 1506-046 (S) Syntax error. > "ncx.h", line 429.59: 1506-046 (S) Syntax error. > "ncx.h", line 429.68: 1506-046 (S) Syntax error. > "ncx.h", line 444.61: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 459.65: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 475.55: 1506-046 (S) Syntax error. > "ncx.h", line 475.64: 1506-046 (S) Syntax error. > "ncx.h", line 490.59: 1506-046 (S) Syntax error. > "ncx.h", line 490.68: 1506-046 (S) Syntax error. > "ncx.h", line 505.61: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 520.65: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 536.53: 1506-046 (S) Syntax error. > "ncx.h", line 536.62: 1506-046 (S) Syntax error. > "ncx.h", line 551.59: 1506-277 (S) Syntax error: possible missing ')' or > ','? > "ncx.h", line 567.55: 1506-046 (S) Syntax error. > "ncx.h", line 567.64: 1506-046 (S) Syntax error. > "ncx.h", line 582.61: 1506-277 (S) Syntax error: possible missing ')' or > ','? > make[2]: *** [attr.o] Error 1 > make[2]: Leaving directory `/usr/common/usg/netcdf/3.4/src/libsrc' > make[1]: *** [subdir_target] Error 1 > make[1]: Leaving directory `/usr/common/usg/netcdf/3.4/src' > make: *** [libsrc/all] Error 2 > > Thanks for your help. I think we need to go one step further and define the C macro "_ALL_SOURCE". Please try the following: 1. Go to the top-level source directory. 2. Perform steps 2 through 5 near the end of the INSTALL file. 3. Ensure that the environment variable CPPFLAGS contains the string "-D_ALL_SOURCE" (I should have told you CPPFLAGS last time too, instead of CFLAGS -- it wouldn't have made any difference, however). 5. Perform steps 6 though 9 near the end of the INSTALL file. Please let me know what you discover. -------- Steve Emmerson <http://www.unidata.ucar.edu>