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.
Franklyn, If you are using csh or tcsh for your command shell, environment variables are set this way: setenv FC opt/pgi/linux86-64/7.0/bin/pgf90 (Note that the command is "setenv", not "sentenv".) If instead you are using bash, sh, or ksh for your command shell, you should set environment variables like this: FC=/opt/pgi/linux86-64/7.0/bin/pgf90 export FC or you can just set the environment variable temporarily right before the command you want to run with that environment variable set, such as FC=/opt/pgi/linux86-64/7.0/bin/pgf90 ./configure --prefix=/usr/local/netcdf If you don't know what command shell you are using, you can just try something like FC=foo and if you are using bash, ksh, or sh, this will be OK, but if you are using csh or tcsh, you will get an error message like FC=foo: Command not found --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: PAB-223364 Department: Support netCDF Priority: Normal Status: Closed