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.
John, > The issue I was trying to resolve was the flags on the Absoft 9.2 > compilier and their interaction with the building of the netcdf library. > A common option used in build fortran codes with absoft is to employ > 2 options: YEXT_NAME and YEXT_SFX which are used for compatibility > with other libraries. It turns out that when using these flags in > building the netcdf library and then a code that uses that library, > these options result in subroutine names that are managled and the > code is unable to find the netcdf routines. I have not tried the > other method, but I think the result is that the library being > build also drops the above options implicitly. The script is just > a way of getting the correct version of netcdf (the beta 3 version) > and setting all the options for tuning and optimization for G5 and > 64-bit (as these are not the defaults). OK, thanks, I included a link to your script here: http://my.unidata.ucar.edu/content/software/netcdf/docs/other-builds.html#absoft Please let me know if you want this changed. --Russ