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.
> > Hi > > > > I want to report a failure for one of the tests (configured with flag > > --enable-large-file-tests) related to netcdf-4.0-snapshot2008021602. Below > > is the output from make check. > > > > I am using Mandriva Linux 2008. If you need more information please let me > > know? > > > > Thanks, Evan > > > > > > PASS: tst_h_rdc0 > > =================== > > All 16 tests passed > > =================== > > make[3]: Leaving directory `/home/emason/python/build/netcdf- > > -I/home/emason/python/build/hdf5-1.8.0-rc2/hdf5//include > > -I../libsrc4 -I../f90 -g -O2 -c -o tst_flarge.o tst_flarge.f90 > > tst_flarge.f90:14.55: > > > > integer, parameter :: MAX_64OFFSET_BYTES = 4294967292 > > 1 > > Error: Integer too big for its kind at (1) > > make[2]: *** [tst_flarge.o] Error 1 > > make[2]: Leaving directory `/home/emason/python/build/netcdf- > > 4.0-snapshot2008021602/nf_test' > > make[1]: *** [check-am] Error 2 > > make[1]: Leaving directory `/home/emason/python/build/netcdf- > > 4.0-snapshot2008021602/nf_test' > > make: *** [check-recursive] Error 1 > > > > Howdy Evan! Looking at your email again, I see that you are getting a build error with gfortran because of a very large integer in the netcdf source code. This is odd, because I test on several versions of gfortran, on several architectures, and I've never seen this bug. Can you tell me what version of gfortran you are using? (gfortran --version). Thanks, Ed Ticket Details =================== Ticket ID: QHK-534643 Department: Support netCDF Priority: Normal Status: Closed