• how to let system aware of the new .so file?

    From Bill@1:0/0 to All on Fri Jan 24 22:39:49 2014
    I am trying to install an customized rpm package. The installation failed with the following error:

    error: Failed dependencies:
    libcrypto.so.6()(64bit) is needed

    In the system there is /usr/lib64/libcrypto.so.10

    So I made a soft link ln -s /usr/lib64/libcrypto.so.10 /usr/lib64/libcrypto.so.6 and reboot the machie. But it seems we cannot fool the OS by simply create a softlink. I think the newer version should have the functions in the old version.

    Thanks

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: The Kofo System II BBS telnet://fido2.kofobbs.
  • From Moe Trin@110:300/11 to All on Sat Jan 25 02:18:32 2014
    On Fri, 24 Jan 2014, in the Usenet newsgroup linux.redhat, in article <2648d671-68f8-409c-96d0-8af0bd49e6eb@googlegroups.com>, Bill wrote:

    NOTE: Posting from groups.google.com (or some web-forums) dramatically
    reduces the chance of your post being seen. Find a real news server.

    I am trying to install an customized rpm package. The installation
    failed with the following error:

    error: Failed dependencies:
    libcrypto.so.6()(64bit) is needed

    In the system there is /usr/lib64/libcrypto.so.10

    http://ibiblio.org/pub/linux/docs/HOWTO/

    -rw-r--r-- 1 gferg users 44071 Oct 10 2008 RPM-HOWTO

    although it actually is from September 2002. You should have a long
    look at the man page (man rpm). "rpm" does not look at the system
    to see what files you have hidden here/there/everywhere - it's a
    package manager, and it looks at a database to see what _packages_
    it has installed, and compares that to what the rpm you are trying to
    install requires. Thus, if you run the command

    rpm -qpR /path/to/name.of.rpm.you.want.to.install.rpm

    it will list what that package wants installed BEFORE you can install
    it. In the old days, this was called "dependency-hell" because
    package A wanted package B, but that needed package C and D, which
    required something else, and so on.

    But it seems we cannot fool the OS by simply create a softlink. I
    think the newer version should have the functions in the old version.

    Has nothing to do with the system - it's totally package manager. If
    you run "rpm -qf /usr/lib64/libcrypto.so.10", it will tell you what
    package ``owns'' that file - you probably need to update that package
    first.

    You _MAY_ be able to work around the package manager by using the
    "--nodeps" option to install it, but you may also horribly break your
    system doing that. USE AT YOUR OWN RISK. You DO have backups, right?
    You can use rpm to find out what is in the package you want to install
    by "rpm -qpl /path/to/name.of.rpm.you.want.to.install.rpm" so you have
    an idea what might get stomped on.

    Old guy

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: Retired Old Pharts of Northern Arizona (110:300/11@linuxnet)