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 Moti, > It works OK if I use compilers/pgi/7.2-5.x86_64 instead of > compilers/pgi/9.0-1. From the "make check" output you sent, it also looked like everything worked OK with the pgi 9.0-1 compilers also, except for the final "make install" step. That step had nothing to do with the compilers, so I'm not sure why things worked better with the older compilers. However, the "make install" failed becasue the configure script had somehow computed that the directory /work/m/mmittal was a "BSD-compatible install program", as this output in config.log shows: checking for a BSD-compatible install... /work/m/mmittal I don't understand how this could have happened. Maybe you have your own "install" or "install.sh" program set in your PATH or maybe you have an INSTALL environment variable set to /work/m/mmittal, but I still don't see how a directory could be mistaken as an executable install probram by the configure script. Try running "make install" in a new subshell, and make sure you don't have any environment variables set to "/work/m/mmittal" in that subshell. If that doesn't work, I'm stumped. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: TXX-423667 Department: Support netCDF Priority: Normal Status: Closed