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.
Gerry, The standard output stream from the configure(1) script (file "configure.log") contained this: checking for library containing XML_StopParser... no configure: error: cannot find EXPAT function XML_StopParser Does the file "/usr/lib64/libexpat.so.1.6.0" on your system contain this symbol? The file "config.log" contained this: configure:4803: cc -o conftest -O -DNDEBUG conftest.c -lexpat >&5 /usr/bin/ld: cannot find -lexpat It would appear, therefore, that cc(1) doesn't check the "/usr/lib64" directory for libraries. There should be a way to configure ld(1) on the system to check the "/usr/lib64" directory. > Here's the attached files. Assuming you wanted to see the full output > (stderr/stdout) captured to configure.log? Otherwise, I don't see one. Regards, Steve Emmerson Ticket Details =================== Ticket ID: LMB-793185 Department: Support UDUNITS 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.