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.
Richard, >Date: Wed, 9 Jul 2003 13:24:33 -0400 (EDT) >From: address@hidden >Organization: North Carolina State University >To: "Steve Emmerson" <address@hidden> >Subject: Re: 20030709: UDUNITS on UCAR's Blackforest IBM The above message contained the following: > Thanks. But, when I comipled my file with -qextname, the problem seem to > be transfered elsewhere. This tme the undefined symbols are the > subroutines calling the udunits library. > > See below( and as usual I do appreciate your feedback) > > ************************************************** > 1501-510 Compilation successful for file ICBC.f. > ld: 0711-317 ERROR: Undefined symbol: .ncopn_ > ld: 0711-317 ERROR: Undefined symbol: .ncvid_ > ld: 0711-317 ERROR: Undefined symbol: .ncainq_ > ld: 0711-317 ERROR: Undefined symbol: .ncagtc_ > ld: 0711-317 ERROR: Undefined symbol: .ncpopt_ > ld: 0711-317 ERROR: Undefined symbol: .ncagt_ > ld: 0711-317 ERROR: Undefined symbol: .ncvgt_ > ************************************************** The undefined symbols above are netCDF routines. This must mean that the Fortran interface of your installed netCDF package must not have underscore suffixes. If the UDUNITS package can be built in the same way, then your problem should be solved. Would you please do the following: 1. Go to the top-level source directory of the UDUNITS package. 2. Perform steps 3 through 7 described near the end of the file INSTALL. 3. Send me the files "configure.log", "config.log", and "make.log" described near the end of the file INSTALL. 4. Send me the output of the following command: nm -g libudunits.a | grep utopen Regards, Steve Emmerson