Thank you all for your help. output of ldd is
> ldd /usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so libamglue.so => /usr/local/lib/amanda/libamglue.so libamanda-2.4.5.so => /opt/sfw/lib/libamanda-2.4.5.so libm.so.2 => /usr/lib/libm.so.2 libgmodule-2.0.so.0 => /usr/local/lib/libgmodule-2.0.so.0 libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0 libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 libpthread.so.1 => /usr/lib/libpthread.so.1 libthread.so.1 => /usr/lib/libthread.so.1 librt.so.1 => /usr/lib/librt.so.1 libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 libiconv.so.2 => /usr/local/lib/libiconv.so.2 libresolv.so.2 => /usr/lib/libresolv.so.2 libintl.so.8 => /usr/local/lib/libintl.so.8 libcrypto.so.0.9.7 => /usr/sfw/lib/libcrypto.so.0.9.7 libnsl.so.1 => /usr/lib/libnsl.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libc.so.1 => /usr/lib/libc.so.1 libgen.so.1 => /lib/libgen.so.1 libcurses.so.1 => /lib/libcurses.so.1 libintl.so.1 => /lib/libintl.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1 libaio.so.1 => /lib/libaio.so.1 libmd.so.1 => /lib/libmd.so.1 libsec.so.1 => /usr/lib/libsec.so.1 libmp.so.2 => /lib/libmp.so.2 libscf.so.1 => /lib/libscf.so.1 libavl.so.1 => /lib/libavl.so.1 libdoor.so.1 => /lib/libdoor.so.1 libuutil.so.1 => /lib/libuutil.so.1 libcrypto_extra.so.0.9.7 => /usr/sfw/lib/libcrypto_extra.so.0.9.7 /platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1 /platform/SUNW,Sun-Fire-V240/lib/libmd_psr.so.1 it all resolves but I do see that libamanda is v2.4.5 and that can't be good. I did a # make uninstall, I'd thought before the build, but I ran it a number of times across a number of builds... do I need to run the make uninstall from my 2.4.5 installation directory ? Is it a matter of changing the order my libraries are specified in, or can I skip /opt/sfw/bin entirely ? Output of the # nm command was not (to me) enlightening, and is probably an artifact of linking the wrong library. > /usr/xpg4/bin/nm -A /opt/sfw/lib/libamanda-2.4.5.so /opt/sfw/lib/libamanda-2.4.5.so: thank you, Brian On Sat, Jan 31, 2009 at 11:08:36AM -0500, Dustin J. Mitchell wrote: > On Sat, Jan 31, 2009 at 9:25 AM, Gunnarsson, Gunnar > <gunnar.gunnars...@svk.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 --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support (v) 518 486-1697 Wadsworth Center (f) 518 473-6384 NYS Department of Health Help Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.