On Sun, 5 Oct 2008, Vijay Lakshmi wrote:

> hi,
> when i try to install sify_bband-3.0-0.i586.rpm in linux the error that it 
> shows is:
> error:Failed dependencies:
> libcrypto.so.0.9.7 is neededby sify_bband-3.0-0.i586
> libssl.so.0.9.7 is needed by sify_bband-3.0-0.i586
> what can i do?
> thanks,
> vijaylakshmi
>


Hi Vijaylakshmi:

Thanks for sending in the sify_bband-3.0-0.i586.rpm

Here are the details of the work i did on the file to understand 
and resolve the dependencies.

# rpm -qpl sify_bband-3.0-0.i586.rpm

/usr/.SifyBband
/usr/.SifyBband/background.png
/usr/.SifyBband/icon.png
/usr/bin
/usr/bin/sifyconnect
/usr/bin/sifyd

Using the rpm2tar command, i created a sify_bband-3.0-0.i586.tar file. 
I used this approach to extract the contents while preserving the 
tree layout.

Next, i ran dependency check on 'sifyd'.

# ldd sifyd
         linux-gate.so.1 =>  (0xffffe000)
         libpthread.so.0 => /lib/libpthread.so.0 (0xb7f66000)
         libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7f38000)
         libssl.so.0.9.7 => not found
         libc.so.6 => /lib/libc.so.6 (0xb7e08000)
         /lib/ld-linux.so.2 (0xb7f9b000)
         libcrypto.so.0.9.7 => not found

# ldd sifyconnect
        shows a lot of dependencies on g* libraries for the gui part.

the RPM file has dependency on openssl-0.9.7. However, today on most 
of the current distros openssl-0.9.8g is shipped.

running '/usr/bin/strace' on sifyconnect shows the following lines 
among others.

...
./sifyd: error while loading shared libraries: libssl.so.0.9.7: cannot 
open shared object file: No such file or directory
waitpid(19200, [{WIFEXITED(s) && WEXITSTATUS(s) == 127}], 0) = 19200
...

The Sify guys have not made an updated release in a long time !

So, one of the possible approach is to "compile" a "suitable" version 
of openssl-0.9.7

  1. decide on a suitable version of openSSL to download from openssl.org
     even for 0.9.7 we got 'a' to 'n' releases.

  2. decide on a version of compiler that is potentially close to the
     time, when sifybb binary were released and also can compile the
        openssl library.

Since, i'm on Gentoo 2008.0 R1 system,
  . i decided to download openssl-0.9.7m which was released in the
    early months of year 2007

  . i 'slot'ed an installation of gcc-3.3.6 and enabled it.
    gcc-4.x is unable to compile openssl-0.9.7m

  . i compiled the openssl library and created the required libraries
    ie. libcrypto.so.0.9.7*  libssl.so.0.9.7*

The good news is that the libraries got compiled successfully and the 
dependency symbols for sifyconnect and sifyd are resolved correctly.

I tried running the sify client and diagnostics checks show this result.
202.144.65.70:8090      SYN_SENT

# netstat -tu

Proto Recv-Q Send-Q Local Address        Foreign Address         State
tcp        0      1 10.10.10.4:58359     sam.sifybroadband.:8090 SYN_SENT

Perhaps sam here stands for 'Sify Access Manager" as evidenced from 
the errors it gave on my system.

CRITICAL::Unable to connect to Sify Access Manager. NO ROUTE to Host!

However, you won't see this error as your system is part of the Sify LAN.

As far as i see, this approach should work for Sify Linux subscribers !

--
Here is the information to help you get started.

1. download sifybb.tar.gz from
    http://www.twincling.org/twincling/downloads/sifybb.tar.gz

2. extract the archive (use the command line)
    tar zxvf sifybb.tar.gz

3. Goto the directory sifybb
    execute the steps specified in README file.

With a little thoughtfulness and perseverance, you should be able to 
get the Sify connection going.


thanks
Saifi.

Reply via email to