Re: Finding Library Dependencies - MxEasy Security Camera Software

[Bob McGowan <bob_mcgowan@symantec.com>]

On 05/09/2011 05:19 AM, CACook@quantum-sci.com wrote:
> On Sunday 8 May, 2011 08:27:27 godo wrote:
>> it's happened sometimes that some package missing in testing or sid but 
>> from my experience it will come in few days or week.
>>
>> If you are in hurry try with sid version and if there is not to much 
>> dependencies I think it wont be a problem.
> 
> I've found libsdl1.2debian-all in Ubuntu Natty, which this software was packaged for, and the only two operative files in it are:
> /usr/lib/libSDL-1.2.so.0
> /usr/lib/libSDL-1.2.so.0.11.3
> 
> There is a libsdl1.2debian-all for Debian Testing, which I'm running, but it's not built for amd64 yet.  There is a libsdl1.2debian-all for squeeze, and it has exactly what Natty's has.
> 
> And the kicker is that libsdl1.2debian (no -all) which I have installed, has these exact files with these exact names as well.  So I think the software is looking for the package name with -all, and when it doesn't find it it fails.  I overrode dependencies and installed it anyway, but inexplicably it does everything but show video.
> 
> There is a way to determine what libraries are required by an executable, but I don't remember what it is.
> 
> 

You want to use:

  $ ldd filename # or libfilename.so or /full/path/lib/libfilename.so

The output will look something like this:

        linux-gate.so.1 =>  (0xb76f4000)
        libclntsh.so.11.1 => not found
        libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7557000)
        /lib/ld-linux.so.2 (0xb76f5000)

Notice here that the second library is "not found".  If you see this,
search for the not found file and put its absolute directory path in
LD_LIBRARY_PATH and repeat the command.

For any library used that is not found in a "standard" location
(minimally /lib:/usr/lib but may include /usr/local/lib), repeat the ldd
on that library to be sure its dependencies are resolved.

-- 
Bob McGowan