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.
Bob, One simple alternative I forgot to mention is to not specify any environment variables for CC, CXX, F77, or F90. Instead, just let the configure script find the compilers to use. This usually works if you have your path set to include directories where the compilers are found. I'm also surprised the configure script didn't catch the attempt to use cc as a C++ compiler, since it supposedly tests whether the C++ compiler works on a simple C++ program. We'll have to check that ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: KGU-334499 Department: Support netCDF Priority: Normal Status: Closed