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.
Clint, The basic problem appears to be that your shell environment still has references to the old GEMLIB location, so that building and linking failed in several places. Note the first 2 lines of your make.out: > Creating /apps/nawips/GEMPAK5.9.1/lib/linux > Creating /apps/nawips/GEMPAK5.9.1/bin/linux These should be /apps/nawips/GEMPAK5.9.1/os/linux/lib /apps/nawips/GEMPAK5.9.1/os/linux/bin The GEMOLB variable used in making the first directory above is defined in $CONFIGDIR/Makeinc.common as $(OS_LIB) in the current distribution- which makes it appear that either you have an old Makeinc.common configuration file (did you copy one from an old distribution where you might have tried configuring for icc before?), or Gemenviron wasn't sourced to correctly define the location of CONFIGDIR for the new distribution. In terms of the configure scripts supplied with the external libraries, it gets quite messy trying to override their attemps to use gcc when available- and that is a big headache when trying to port to other compilers. We don't have a licence for the I-compilers other than the LEAD machines, which had to be purchased on a per node basis, rather than a site license; so it won't be a configuration I can test on here. Not all vendors allow us to be an "edu" site in that regard. Steve Chiswell Unidata User Support Ticket Details =================== Ticket ID: DCW-658829 Department: Support GEMPAK Priority: High Status: Closed