On Sat, Jan 31, 2009 at 9:25 AM, Gunnarsson, Gunnar
<Gunnar.Gunnarsson AT svk DOT se> wrote:
> I got the same problem
>> ldd usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so | grep amanda
>        libamglue.so =>  /opt/sfw/lib/amanda/libamglue.so
>        libamanda-2.5.2p1.so =>  /opt/sfw/lib/libamanda-2.5.2p1.so
> I had older version installed on the system and build with 
> LDFLAGS=-L/opt/sfw/lib -R/opt/sfw/lib which has
> worked for eralier version such as 2.6.1b2-20090108 etc.

Obviously, inter-linking different Amanda versions like this is going
to be problematic.

This sort of thing happens sometimes on my development systems, where
I'm running the latest release of Amanda (in /usr/), but of course
developing the bleeding edge.

The key thing to note is that Amanda is "selecting" a library version
at install time; you'll note in the above ldd output that ldd is
searching not just for libamanda, but for libamanda-2.5.2p1.

I'm sure there are several ways to solve this, but the one that comes
to mind is simply removing the old amanda libraries from /opt/sfw/lib
before running 'make install' to install the new libraries.

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com