|
Home > Archive > Red Hat Topics > July 2006 > libssl.so.5 in FC5
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
libssl.so.5 in FC5
|
|
| Gwen Morse 2006-07-16, 7:12 pm |
| When trying to update enlightenment recently (just after upgrading to
FC5), I got an error message that assorted packages needed
libcrypto.so.5 and libssl.so.5.
I found an rpm with libssl.so.0.9.7f and libcrypto.so.0.9.7f, moved
those two files to /lib, and made soft links for libcrypto.so.5 and
libssl.so.5.
However, enlightenment still tells me I need those two lib files. Is
there something more that needs to be done? I don't want to uninstall
the .6 files as too many fc5 apps need them. I just want them to be
able to peacefully coexist. I still have .4 files without any
conflicts.
Gwen
--
Gwen Morse mailto:goldmooneachna@yahoo.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Love is a snowmobile racing across the tundra and then
suddenly it flips over, pinning you underneath. At night,
the ice weasels come." -- Matt Groening
--
Posted via a free Usenet account from http://www.teranews.com
| |
| Ed Hurst 2006-07-17, 1:12 am |
| Gwen Morse wrote:
> When trying to update enlightenment recently (just after upgrading to
> FC5), I got an error message that assorted packages needed
> libcrypto.so.5 and libssl.so.5.
>
> I found an rpm with libssl.so.0.9.7f and libcrypto.so.0.9.7f, moved
> those two files to /lib, and made soft links for libcrypto.so.5 and
> libssl.so.5.
I don't know all the ins and outs. However, in times past, I have been
able to create softlinks labeled as the older version and make things
work. It's likely they are backward compatible.
Ed Hurst
----------
return addy is a spam trap
try je hurst at gmail dot com
| |
|
| Yes, Ed. In many cases the RPM packager specified a particular library
version instead of a plain vanilla version ending in *.so. That's one of
the differences between free software and a proprietary UNIX version.
My solution, which has never yet failed -- knock on wood -- is to softlink
whatever the packager specified to *.so while ensuring the most current
library version is also softlinked to *.s
e.g.:
ln -s libssl.so.0.9.7f libssl.so
ln -s libssl.so libssl.so.5
--
Lubow
"Ed Hurst" <me@privacy.net> wrote in message
news:dNCug.49717$VE1.39230@newssvr14.news.prodigy.com...
> Gwen Morse wrote:
>
> I don't know all the ins and outs. However, in times past, I have been
> able to create softlinks labeled as the older version and make things
> work. It's likely they are backward compatible.
>
> Ed Hurst
> ----------
> return addy is a spam trap
> try je hurst at gmail dot com
|
|
|
|
|