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.
Hi Kwan, re: > It appeared that I got the same error after following the steps you > indicated. In the last part of makelog excerpt you sent, I see that for some reason your build is attempting to use the system-installed libz: /export-5/ncosrvnfs-cp/nawips1/os/linux2.6.32_x86_64/lib/libz.a: could not read symbols: Bad value Now the question is why your build is trying to use a system-installed libz.a when the make file says to use the one built in the McIDAS distribution? Please send me the output of the following: env Question: - did you follow the instructions in the page I sent earlier that describes how to set the environment by reading the ~mcidas/admin/mcidas_env.(csh|sh) file(s)? Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: LOB-532260 Department: Support McIDAS Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.