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.
> I forgot the output from ./configure > > configure: netCDF 4.0.1 > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > configure: checking user options > checking whether CXX is set to ''... no > checking whether FC is set to ''... no > checking whether F90 is set to ''... no > checking whether a NCIO_MINBLOCKSIZE was specified... 256 > checking whether this is a netCDF-4.x build... yes > checking whether extra valgrind tests should be run... no > configure: Processing NetCDF-4 options. > checking whether netCDF-4 is to be built... no > checking whether new netCDF-4 C++ API is to be built... no > checking whether HDF5 should do data conversions... no > checking whether extra example tests should be run... no > checking whether parallel IO tests should be run... no > checking whether a location for the HDF5 library was specified... > checking whether a location for the ZLIB library was specified... > checking whether a location for the SZLIB library was specified... > checking whether a default cache size for HDF5 was specified... 32000000 > checking whether a default cache maximum number of elements for HDF5 was > specified... 1000 > checking whether a default cache preemption for HDF5 was specified... 0.75 > checking whether netCDF-4 logging is enabled... no > checking whether DAP client is to be built... no > checking whether dap remote testing should be enabled... no > checking whether netCDF extra tests should be run (developers only)... no > checking whether documentation is to be installed... no > checking whether Fortran compiler(s) should be tested during configure... yes > checking whether FFIO will be used... no > checking whether to skip C++, F77, or F90 APIs if compiler is broken... yes > checking whether only the C library is desired... no > checking whether examples should be built... yes > checking whether F77 API is desired... yes > checking whether F90 API is desired... yes > checking whether fortran type sizes should be checked... yes > checking whether C API is desired... yes > checking where to get netCDF C-only library for separate fortran libraries... > checking whether CXX API is desired... yes > checking whether v2 netCDF API should be built... yes > checking whether the ncgen/ncdump should be built... yes > checking whether large file (> 2GB) tests should be run... no > checking whether benchmaks should be run (experimental)... no > checking whether extreme numbers should be used in tests... yes > checking where to put large temp files if large file tests are run... . > checking whether a win32 DLL is desired... no > checking whether separate fortran libs are desired... no > configure: finding C compiler > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... no > checking whether pgcc accepts -g... yes > checking for pgcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of pgcc... none > checking whether pgcc and cc understand -c and -o together... yes > checking for an ANSI C-conforming const... yes > configure: finding Fortran compiler (will not be used if Fortran API is not > desired) > checking whether we are using the GNU Fortran compiler... no > checking whether pgf90 accepts -g... yes > checking whether we are using the GNU Fortran 77 compiler... no > checking whether pgf77 accepts -g... yes > configure: setting up Fortran 90 > checking for Fortran flag to compile .f90 files... none Can you try the 4.1 release, which I just put up on the website? Thanks, Ed Ticket Details =================== Ticket ID: PRG-103154 Department: Support netCDF Priority: Normal Status: Closed