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.
Dan, > To: address@hidden > From: address@hidden (Dan Schmitt) > Subject: NetCDF and IRIX64 6.2 > Organization: Department of Rangeland Ecology and Management / Texas A&M > University > Keywords: 199607302242.AA26860 In the above message you wrote: > Our IRIX64 system just got upgraded. > It broke the netCDF stuff. > > (uname -a = IRIX64 terminator 6.2 03131016 IP25 ) > > I did the fix for the configure script > that changes the irix64 HAS_XDR_GETINT=1;; > to HAS_XDR_GETINT=0;; > > ... > > During a "make test" I get: > > ar rcuv libnetcdf.a array.o attr.o cdf.o dim.o file.o iarray.o error.o > globdef.o > putget.o putgetg.o sharray.o string.o var.o xdrposix.o > case "" in \ > '') ;; \ > *) ar rucv libnetcdf.a ;; \ > esac > : libnetcdf.a > cc -o cdftest -O cdftest.o libnetcdf.a > ./cdftest > cdftest_out.new > Segmentation fault - core dumped > make[1]: *** [test] Error 139 > make[1]: Leaving directory > `/medium/ranch/develop.terminator/work2/remote-pack/n > etcdf-2.4.2/src/libsrc' > make: *** [libsrc/test] Error 1 > > and a debugger run shows: > > Assuming return register value (0xda659a0) usable to locate PC. > Core from signal SIGSEGV: Segmentation violation > (dbx) where > > 0 _xdr_int(0x10023850, 0xffffffa718, 0x0, 0x1, 0x8bc, 0x2, 0x0, 0xdb441f0) > > ["/xlv4/patches/1457/work/irix/lib/libc/libc_64_M4/rpc/xdr.c":109, > > 0xda659a0] > 1 _xdr_enum(0x10023850, 0xffffffa718, 0x0, 0x1, 0x8bc, 0x2, 0x0, > 0xdb441f0) ["/xlv4/patches/1457/work/irix/lib/libc/libc_64_M4/rpc/xdr.c":439, > 0xda66070] > 2 xdr_NC_array(0x10023850, 0x10023830, 0x0, 0x1, 0x8bc, 0x2, 0x0, > 0xdb441f0) > ["/medium/ranch/develop.terminator/work2/remote-pack/netcdf-2.4.2/src/libsrc/array.c":519, > 0x10008d48] > 3 xdr_cdf(0x10023850, 0xffffffabf8, 0x43444601, 0x1, 0x8bc, 0x2, 0x0, > 0xdb441f0) > ["/medium/ranch/develop.terminator/work2/remote-pack/netcdf-2.4.2/src/libsrc/cdf.c":257, > 0x10005d7c] > 4 NC_endef(0x0, 0x0, 0x10023400, 0x1, 0x8bc, 0x2, 0x0, 0xdb441f0) > ["/medium/ranch/develop.terminator/work2/remote-pack/netcdf-2.4.2/src/libsrc/file.c":648, > 0x100075b8] > 5 ncendef(0x0, 0xffffffa718, 0x0, 0x1, 0x8bc, 0x2, 0x0, 0xdb441f0) > ["/medium/ranch/develop.terminator/work2/remote-pack/netcdf-2.4.2/src/libsrc/file.c":773, > 0x10007a3c] > 6 main(0x10023850, 0xffffffa718, 0x100222a8, 0x100222c0, 0x8bc, 0x2, 0x0, > 0xdb441f0) > ["/medium/ranch/develop.terminator/work2/remote-pack/netcdf-2.4.2/src/libsrc/cdftest.c":419, > 0x10003fb4] > 7 __start() > ["/vince/6.2-mar09/work/irix/lib/libc/libc_64_M4/csu/crt1text.s":166, > 0x10002f38] > > and then the netcdf.h says you may need to customize the USE_ENUM for your > location, and so I tried it without USE_ENUM defined, and it failed in > array.c at line 524 (according to the debugger.) > > Any suggestions on what I should try next? I suggest that you try an alpha-test version of the netCDF package. It works on our IRIX64 6.2 system. The package is available at the following URL: ftp://ftp.unidata.ucar.edu/pub/netcdf/alpha.tar.Z Note that it doesn't contain a User's Guide. You'll have to use the one in your existing doc/ subdirectory. Please let me know if this helps. -------- Steve Emmerson <address@hidden>