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

[UDUNITS #PPU-703715]: bug when linking to libudunits2.1.13 + solution

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 #PPU-703715]: bug when linking to libudunits2.1.13 + solution
  • Date: Wed, 27 Jan 2010 08:46:09 -0700
Jisk,

> i am compiling udunits 2.1.13 (and want to use it for nco-4.0.0), but
> linking to the library fails:
> The program udunits2 works, but libudunits2.so contains unresolved
> symbols (all the expat functions starting with XML_*).
> 
> I could solve this by adding:
> 
> libudunits2_la_LIBADD = ../expat/libexpat.la
> 
> to udunits2.1.13/lib/Automake.am (and running autoreconf etc.)

Sorry about that.

Your solution is workable.  An alternative would be to modify the Expat 
makefile to install the Expat library in the same installation directory as the 
UDUNITS-2 library.  This would allow users to use a different Expat library if 
they so choose (one that's been updated for security reasons, for example).

Do you have an opinion on which is preferable?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: PPU-703715
Department: Support UDUNITS
Priority: Normal
Status: Closed