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.
Pascale, > From: Pascale Lherminier <address@hidden> > Subject: netcdf installation failed > Organization: Naval Postgraduate School > Keywords: 200005121845.e4CIj9415880 netCDF Cray J90 f90 C++ In the above message, you wrote: > After several tries, I could not figure out why the installation > of the netcdf library failed. My goal was to install it on > my private directory first to make a couple of compatibility > tests and use it for the outputs of our model ... but 'make' > failed. Perhaps is it due to older versions of C,C++ and F90 > than those you used to test the installation ...? > So here are the informations you ask for in such a case: > > Machine specifications: > > jedi jedi 10.0.0.6 roo.0 CRAY J90 > Cray Standard C Version 5.0.3.0 (d29p35g115a35) May 12 2000 10:59:39 > Cray C++ Version 2.0.3 05/12/00 10:59:46 > Cray CF90 Version 2.0.3.0 05/12/00 10:59:54 > > Version : 3.4 > All the compilers are in /opt/ctl/bin > (cc, f90 and CC). > > ------------------------------------------------------------ > > The job I submitted to install netcdf: > > # QSUB -q reg > # QSUB -lT 20000 > # QSUB -lM 40Mw > # QSUB -me -mb > # QSUB -e netcdf.err > # QSUB -o netcdf.out > # > ja > setenv CC /opt/ctl/bin/cc > setenv CPPFLAGS > setenv CFLAGS -O3 > setenv FC /opt/ctl/bin/f90 > setenv FFLAGS "-g -F -dp" > setenv CXX /opt/ctl/bin/CC > setenv CXXFLAGS > > cd /u0/pascale/netcdf-3.4/src > #cd libsrc > #cp ncx.c ncx.c.old > #cp ncx_cray.c ncx.c > #cd .. > ./configure > make > #make test > #make install > > ja -st > > # done. > exit 0 > > -------------------------------------------------------------- > > I attached config.log, and also the output and error files to > this e-mail. > > Thank you very much for you help and the very good explanations > in the INSTALL file. > > Best regards, > Pascale Lherminier. > > > -- > Pascale Lherminier | Tel.: (int) (1) (831) 656 3260 > Dpt of Oceanography | Fax.: (int) (1) (831) 656 2712 > Naval Postgraduate School | E-mail : address@hidden > Monterey, CA93943, USA | http://www.oc.nps.navy.mil/opbl > --------------3A9BD479F27089BA558E59AD > Content-Type: text/plain; charset=us-ascii; > name="netcdf.out" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline; > filename="netcdf.out" > > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "/opt/ctl/bin/cc" > checking C compiler... works > checking how to make dependencies... false > checking for /opt/ctl/bin/CC... /opt/ctl/bin/CC > checking C++ compiler "/opt/ctl/bin/CC"... works > checking how to run the C preprocessor... /opt/ctl/bin/cc -E > checking user-defined Fortran compiler "/opt/ctl/bin/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"... yes > checking for Fortran "integer*2"... yes > checking if Fortran "integer*1" is C "signed char"... no > checking if Fortran "integer*1" is C "short"... yes > checking if Fortran "integer*1" is C "int"... yes > checking if Fortran "integer*1" is C "long"... yes > checking if Fortran "integer*2" is C "short"... yes > checking if Fortran "integer*2" is C "int"... yes > checking if Fortran "integer*2" is C "long"... yes > 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"... integer*1 > 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... no > checking for working ftruncate()... no > checking for working alloca.h... no > checking for alloca... no > checking whether alloca needs Cray hooks... yes > checking for _getb67... yes > checking stack direction for C alloca... 1 > checking for st_blksize in struct stat... yes > checking for IEEE floating point format... no > 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... 8 > checking size of int... 8 > checking size of long... 8 > checking size of float... 8 > checking size of double... 8 > checking size of off_t... 8 > checking size of size_t... 8 > checking for catman... no > checking for makewhatis... no > checking for manual-page index command... > 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 > > Making `all' in directory /u0/pascale/netcdf-3.4/src/libsrc > > /opt/ctl/bin/cc -c -O3 -I. attr.c > /opt/ctl/bin/cc -c -O3 -I. dim.c > /opt/ctl/bin/cc -c -O3 -I. error.c > /opt/ctl/bin/cc -c -O3 -I. -DVERSION=`cat ../VERSION` libvers.c > /opt/ctl/bin/cc -c -O3 -I. nc.c > /opt/ctl/bin/cc -c -O3 -I. ncio.c > /opt/ctl/bin/cc -c -O3 -I. ncx.c > /opt/ctl/bin/cc -c -O3 -I. putget.c > > Traceback initiated at "output_msg"+01056a (P = 0407213d, line 506) > > "output_msg" called by "PRINTMSG" (P = 0406126c, line 196) with 5 arguments > 1) 0000000000000000023777 -> (0000000000000001557503 = 450371) > 2) 0000000000000000020065 -> (1777777777777777777740 = -32) > 3) 0000000000000000000005 -> (0001641105526760312266 = '_t$Z____') > 4) 0000000000000000000000 -> (0) > 5) 0000000000000000513241 -> (0000000000000000200467 = 65847) > "PRINTMSG" called by "SORTED_PRINTMSG" (P = 01717515c, line 1314) with 8 > arguments > 1) 0000000000000000023777 -> (0000000000000001557503 = 450371) > 2) 0000000000000000020065 -> (1777777777777777777740 = -32) > 3) 0000000000000000000005 -> (0001641105526760312266 = '_t$Z____') > 4) 0000000000000000000000 -> (0) > 5) 0000000000000000200467 -> (0401001623446115033137 = '@@99146_') > 6) 0200000000000000200527 = 0200000000000000200527 = ' ______W' > 7) 0400000000000000200567 = 0400000000000000200567 = '@______w' > 8) 0600000000000000200627 = 0600000000000000200627 = '`_______' > "SORTED_PRINTMSG" called by "cmcs_message" (P = 02223076c, line 409) with 8 > arguments > 1) 0000000000000000023777 -> (0000000000000001557503 = 450371) > 2) 0000000000000000020065 -> (1777777777777777777740 = -32) > 3) 0000000000000000000005 -> (0001641105526760312266 = '_t$Z____') > 4) 0000000000000000000000 -> (0) > 5) 0000000000000000200467 -> (0401001623446115033137 = '@@99146_') > 6) 0200000000000000200527 = 0200000000000000200527 = ' ______W' > 7) 0400000000000000200567 = 0400000000000000200567 = '@______w' > 8) 0600000000000000200627 = 0600000000000000200627 = '`_______' > "cmcs_message" called by "ccg_ref" (P = 02215044a, line 7450) with 1 > argument > 1) 0000000000000000020065 -> (1777777777777777777740 = -32) > "ccg_ref" called by "stidx_val" (P = 0542764d, line 6328) with 5 arguments > 1) 0000000000000005274175 -> (0700000000000000000000 = 'p_______') > 2) 0000000000000000000000 -> (0) > 3) 0000000000000000000000 -> (0) > 4) 0000000000000000000041 -> (0) > 5) 0000000000000000000000 -> (0) > "stidx_val" called by "gen_a_call" (P = 0540671d, line 5816) with 3 arguments > 1) 0000000000000000000663 -> (0445221006155733473145 = 'IR conve') > 2) 0000000000000000000001 -> (9) > 3) 0000000000000000000002 -> (0000000000000000507315 = 167629) > "gen_a_call" called by "gen_asg" (P = 0532706a, line 4578) with 3 arguments > 1) 0000000000000000000001 -> (9) > 2) 0000000000000000513005 -> (0000000000000015372041 = 3535905) > 3) 0000000000000000000000 -> (0) > "gen_asg" called by "process_func_body" (P = 0525150d, line 3228) with 3 > arguments > 1) 0000000000000000000013 -> (0000000000000000315472 = 105274) > 2) 0000000000000000512756 -> (14) > 3) 0000000000000000000000 -> (0) > "process_func_body" called by "PDGCS_do_proc" (P = 01270174a, line 3002) > with 1 argument > 1) 0000000000000000000345 -> (0) > "PDGCS_do_proc" called by "generate_pdg" (P = 066230c, line 322) with 0 > arguments > "generate_pdg" called by "main" (P = 0171522d, line 341) with 4 arguments > 1) 0000000000000000015145 -> (0) > 2) 0000000000000000015146 -> (0) > 3) 0000000000000000000011 -> (0) > 4) 0000000000000000507315 -> (0000000000000000507414 = 167692) > "main" called by "$START$" (P = 02751402c, line 389) with 3 arguments > 1) 0000000000000000000011 -> (0) > 2) 0000000000000000507315 -> (0000000000000000507414 = 167692) > 3) 0000000000000000507327 -> (0600000000000000507434 = '`_______') "/opt/ctl/bin/cc" fails to compile "libsrc/putget.c", eh? We've had some problems before compiling that file on J90-s, though they didn't have the same symptoms as yours. Try dropping into the "libsrc/" directory and executing the following command manually: /opt/ctl/bin/cc -c -O2 -I. putget.c (This is the same command that failed before except that the "-O3" option has been replaced with "-O2".) Does it work? Regards, Steve Emmerson <http://www.unidata.ucar.edu>