Amanda-Users

Re: Amanda 2.6.1 on Solaris x86 - library dependency

2009-08-14 15:37:38
Subject: Re: Amanda 2.6.1 on Solaris x86 - library dependency
From: Chris Hoogendyk <hoogendyk AT bio.umass DOT edu>
To: Brian Cuttler <brian AT wadsworth DOT org>
Date: Fri, 14 Aug 2009 14:12:25 -0400


Dustin J. Mitchell wrote:
On Fri, Aug 14, 2009 at 1:22 PM, Brian Cuttler<brian AT wadsworth DOT org> 
wrote:
They look like the same binary but don't act like the same binary.

This is really best handled by those who are skilled in the ways of
Solaris -- the operating system has lots of weird behaviors with
regard to linking.  What's happening is that amandad is recording a
link to 'libamanda', which ldd is then resolving to the first
libamanda it finds, which happens to be the really old one on cascade.

Two possible solutions:
 - delete the old libraries
 - make sure the linker does not look in the directory containing the
old libraries (/opt/sfw/lib) by removing it from various LD_foo_PATH
variables (some of which are specified at compile time, IIRC).

If you use `ldd -s` it will display the search path it uses to find the libraries (I believe the examples you showed just used ldd). That will tell you how it is getting there. Then you can modify it from that point. One option is to remove the older 2.4.5 library if you don't need it anymore.

It's the combination of how you built the binary, what your LD_LIBRARY_PATH is in the particular environment it is running in, and how crle is set up. Depending on where your newer library is compared to your older library, you can adjust those so that it finds the newer library first.

--
---------------

Chris Hoogendyk

-
  O__  ---- Systems Administrator
 c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<hoogendyk AT bio.umass DOT edu>

---------------
Erdös 4



<Prev in Thread] Current Thread [Next in Thread>