Fwd: Re: [OTR-users] otr plugin doesn't show up

[Faber]

On Sun, 02 Apr 2006 09:34:49 -0400, "Greg Troxel" <gdt at ir.bbn.com> said:
> You didn't mention what system you are using (VMS?  DG-UX? AIX?
> Solaris? :-).  

Haha, sorry, it was late when I wrote that message so I didn't put in
everything I should have.  I'm running Debian Stable (Sarge) on my old
Thinkpad 600E with a 2.4.27 kernel.

> But, the error message indicates that whe gaim tried to
> dynamic link the plugin, some libaries couldn't be resolved.
> 
> Try doing
> 
>  ldd /usr/local/lib/giam/gaim-otr.so
> 
> On my system (NetBSD, still with older OTR), I get
> 
> gdt 144 ~ > ldd /usr/pkg/lib/gaim/gaim-otr.so 
> /usr/pkg/lib/gaim/gaim-otr.so:
>         -lintl.0 => /usr/lib/libintl.so.0
>         -lgpg-error.0 => /usr/pkg/lib/libgpg-error.so.0
>         -lgcrypt.11 => /usr/pkg/lib/libgcrypt.so.11
>         -lotr.1 => /usr/pkg/lib/libotr.so.1
> 
> 
> Likely problems are that libotr.so is not really in /usr/local/lib,
> that /usr/local/lib is not in the default library search path, or that
> gaim-otr was built without the correct -rpath settings.


when I run ldd, I get the following:

hackstock:/home/faber# ldd /usr/local/lib/gaim/gaim-otr.so 
        libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x40018000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x40065000)
        libotr.so.2 => /usr/lib/libotr.so.2 (0x4006a000)
        libc.so.6 => /lib/libc.so.6 (0x40079000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x401ac000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

Now, if I'm right, gaim was looking for libotr in /usr/lib/.  I poked
around on the Debian website for a while, and found the .deb package for
a slightly older version of libotr, and it showed that when installed,
it places libotr.so.2 into /usr/lib.  So, I cp'd libotr.so.2 into
/usr/lib -- and it instantly showed up in the gaim plugins list when I
restarted -- and didn't throw any error messages.  I was able to
establish an encrypted chat session with another friend who has the same
version of OTR running, and all seems to be well.