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.
> This afternoon I downloaded (netcdf-3.6.2-beta4) > 4305871 Nov 28 16:53 netcdf-beta.tar.gz > > and hit a snag when: > > make: *** No rule to make target `extra_check'. Stop. > > I intend to manipulate large files, so I'd like to check the support. > In a nutshell -- here is my build process with gcc & g77 on an x86_64 > machine. > > > ./configure --prefix=${PREFIX} --with-temp-large=/ptmp/thoar || exit 1 > > make || exit 2 > make check || exit 3 > make extra_check || exit 4 > make install || exit 5 > > configure/make/make check all work just perfect -- as far as I can tell. > The INSTALL document indicates this is still a good idea. > > Any suggestions? > > Tim Hoar, Associate Scientist > National Center for Atmospheric Research > address@hidden > 303 497 1708 > > > Howdy Tim! To conform with standard autoconf/automake practices, I took out the make extra_check target. But you can still run these tests. To get the large file tests, use the --enable-large-file-tests with configure, and then the large file tests will be run when "make check" is run. Take a look also at the --with-temp-large=/somewhere option too. It allows you to specify a location for the temporary large files to be created. Specifying a local (i.e. not NFS mounted) disk will save you time and network wear and tear. I see that this is not mentioned in the current documentation on line, but that is a documentation bug that has been fixed for the next beta release. Let me know if this doesn't work for you, and keep on netCDFing! Ed Ticket Details =================== Ticket ID: KEK-710535 Department: Support netCDF Priority: Normal Status: Closed