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, [I just received both your email and phonemail messages.] > To: address@hidden > cc: Harsh Anand <address@hidden> > From: Harsh Anand <address@hidden> > Subject: netcdf-3.4 installation make fails on IBM RS/6000 > Organization: LBNL/NERSC > Keywords: 199908302133.PAA20130 In the above message, you wrote: > I am trying to install netcdf-3.4 on IBM RS/6000 and make fails. > Please see the information appended below. > > Thanks for your help. > > Harsh > > -- > Harsh Anand ---------------------------------- address@hidden -| > NERSC User Services phone: (510) 486-5575 | > Lawrence Berkeley Lab Fax: (510) 486-7520 | > Univ. of California, Berkeley ------------------------------------ > > Here are the list of environment variables that I set before > runnning the script Configure: > > setenv CC xlc > setenv CPPFLAGS -DNDEBUG > setenv CFLAGS -O > setenv FC xlf > setenv FFLAGS -O > setenv CXX KCC > setenv LIBS /lib/libm.a > > > uname -a > AIX d100103 3 4 000034254C00 > > > > cat VERSION > 3.4 > > > which xlf > /bin/xlf > > > which xlc > /usr/vac/bin/xlc > > > which KCC > /usr/common/usg/KCC/3.4b/KCC_BASE/bin/KCC > > >cat 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... no Odd. The answer to the last test above is "yes" on our AIX 4.3 RS/6000 system. Would you please send me the file "config.log", which was created by the configure script. > 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... no > 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 > > > cat 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 -I. -DNDEBUG attr.c > xlc -c -O -I. -DNDEBUG dim.c > xlc -c -O -I. -DNDEBUG error.c > xlc -c -O -I. -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c > xlc -c -O -I. -DNDEBUG nc.c > xlc -c -O -I. -DNDEBUG ncio.c > xlc -c -O -I. -DNDEBUG ncx.c > "ncx.c", line 1119.2: 1506-205 (S) #error "ix_float implementation" > "ncx.c", line 1542.2: 1506-205 (S) #error "ix_double implementation" > make[2]: *** [ncx.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 > > -- > Harsh Anand ---------------------------------- address@hidden -| > NERSC User Services phone: (510) 486-5575 | > Lawrence Berkeley Lab Fax: (510) 486-7520 | > Univ. of California, Berkeley ------------------------------------ -------- Steve Emmerson <http://www.unidata.ucar.edu>