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.
Daniel, > Yes. That was the same code that worked before on Mandrake Linux and PGI > Compilers. > > Now that I remember, udunits didn't go through the make successfully > without the -DpgiFortran flag. I had a problem earlier with unresolved > intrinsics with the udunits library, so I used the following command > (similar to netCDF) to run configure and build the udunits successfully. > > ./configure --prefix=/var/local/udunits --enable-f77 --enable-f90 > LDFLAGS=-lifcore CPPFLAGS="-DNDEBUG -DpgiFortran" The options you specified to the configure(1) script will result in a successful build. The "--enable-f77" and "--enable-f90" options were ignored, however. > However, now I am running into this problem. I am thinking of building > udunits with gcc instead of icc and compile my program with ifort with gcc > compatibility. Please let me know if you have any suggestions on this. I suspect that switching to gcc(1) won't solve the problem (but please try) because I suspect the problem is due to a change in ifort(1)'s calling conventions. If switching doesn't work, then would you please 1. Go into the "src/lib" directory. 2. Execute the command "make utlib.i" -- redirecting both the standard output and standard error streams into the file "utlib.log". 3. Send me the files "utlib.log" and "utlib.i". > Thanks, > > Daniel. Regards, Steve Emmerson Ticket Details =================== Ticket ID: NDS-204592 Department: Support UDUNITS Priority: Normal Status: Closed