[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[UDUNITS #LMB-793185]: Problems installing udunits 2.2.25

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.

  • Subject: [UDUNITS #LMB-793185]: Problems installing udunits 2.2.25
  • Date: Wed, 15 Nov 2017 15:22:41 -0700
Gerry,

> I looked at that yesterday before sending in the help request. Look here:
> odin1:~ # ls /usr/lib64/libexpat*
> /usr/lib64/libexpat.so  /usr/lib64/libexpat.so.1
> /usr/lib64/libexpat.so.1.6.0

Yes, but does that shared library contain the symbol "XML_StopParser"? Use the 
nm(1) utility to find out.

> > There should be a way to configure ld(1) on the system to check the
> > "/usr/lib64" directory.
> 
> So, let's look at ldconfig's cache:
> odin1:~ # ldconfig -p|grep expat
> libexpat.so.1 (libc6,x86-64) => /usr/lib64/libexpat.so.1
> libexpat.so.1 (libc6) => /usr/lib/libexpat.so.1
> libexpat.so (libc6,x86-64) => /usr/lib64/libexpat.so
> libexpat.so (libc6) => /usr/lib/libexpat.so
> 
> It should find it, I'd think, except, I now see it's not seeing
> libexpat.so.1.6.0, which IS in there:
> 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, you're telling me that, instead of looking for the simple .so, it's
> really looking for a specific release? That's a bit of a problem.

The "-lexpat" argument should cause the linker to find the 
"/usr/lib64/libexpat.so" symbolic-link to the "/usr/lib64/libexpat.so.1.6.0" 
dynamic library. The fact that it's not is very strange.

You might try adding "/usr/lib64" to the environment variable LD_LIBRARY_PATH 
before executing the configure(1) script. Let me know if this works.

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.