[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: Thu, 28 Jan 2010 17:09:28 -0700
Jisk,

> The best solution would be to make expat a dependency, and always use
> the system installed one. However,
> 
> * the current manual says to 'link using -ludunits' and doesn't mention
> expat anywhere so it then needs to be updated
> * the 'udunits2' commandline program is statically linked to the expat
> program that comes with udunits. so this would have to be changed, too.
> 
> 
> The easiest solution (ie. least amount work) is the one i proposed, but
> i cant judge the security issues (probably not an issue?).

I'm about to release a new distribution that will check for the existence of an 
Expat library on the host system and only build (and install) the Expat library 
that comes with the UDUNITS-2 package if one doesn't already exist.

I've also documented that "-lexpat" will be necessary for linking.

Thanks for sending this in.

> regards,
> 
> jisk

Regards,
Steve Emmerson

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