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.
Hey Gerry! Send me the output from running the configure(1) script (e.g., the files "configure.log" and "config.log"). "configure.log" should indicate what couldn't be found and "config.log" should show where it looked. > Looking at 2.2.25 from source, and I'm trying to install on a new Cray > with, nominally, SuSE Ent 12. > libexpat and the devels are installed: > rpm -qa|grep libexpat > libexpat1-2.1.0-20.2.x86_64 > libexpat1-32bit-2.1.0-20.2.x86_64 > libexpat-devel-2.1.0-20.2.x86_64 > > However, like Peter's from 2015, configure is just not finding the lib. > > ll /usr/lib64/libexpat* > lrwxrwxrwx 1 root root 17 Nov 2 15:14 /usr/lib64/libexpat.so -> > libexpat.so.1.6.0 > lrwxrwxrwx 1 root root 17 Nov 2 15:10 /usr/lib64/libexpat.so.1 -> > libexpat.so.1.6.0 > -rwxr-xr-x 1 root root 170200 Feb 2 2017 /usr/lib64/libexpat.so.1.6.0 > > So we at least suspect the libs are there. Any thoughts? 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.