When I try to rpm -i for MySQL 4.1, I get:

[root@sforsgren-linux-01 MySQL_4.1]# rpm -i MySQL-sh*
warning: MySQL-shared-4.1.0-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5error: Failed dependencies:
libcrypto.so.0.9.6 is needed by MySQL-shared-4.1.0-0
libssl.so.0.9.6 is needed by MySQL-shared-4.1.0-0

Though, I have both in /usr/lib. Why is it not looking there? Do I need to add that to my PATH or ?

the path isn't relevant, the information is kept in the rpm database try a query like "rpm -qf openssl" to see what rpm *thinks* is there.

When I do that, I get

[root@sforsgren-linux-01 MySQL_4.1]# !r
rpm -qf openssl
error: file openssl: No such file or directory

When I do this:

[root@sforsgren-linux-01 MySQL_4.1]# rpm -qa | grep openssl
openssl096-0.9.6-17
openssl-devel-0.9.7a-5
openssl096b-0.9.6b-6
openssl-perl-0.9.7a-5
openssl-0.9.7a-5

So, it doesn't see openssl at all, right? How do I tell it about it?

Here are the files I have in /usr/lib:

[root@sforsgren-linux-01 lib]# ls libss*
libss.a libssl.a libssl.so.0.9.6 libss.so
libssl3.so libssl.so libssl.so.1
[root@sforsgren-linux-01 lib]#


Thanks

You just answered your own question
mate :)

The version numbers don't match ;)

And man, rpm is sooooo utterly, unforgivingly stupid



Cheers,
Tink

So, even though I have the file:

/usr/lib/libssl.so.0.9.6

and RPM says it is looking for:

libssl.so.0.9.6 is needed by MySQL-shared-4.1.0-0

How do I not have the right version? Where did the file come from if I don't have the correct version?

What do I need to do to correct this? All I am trying to do is install MySQL 4.1.

Thanks!

They are -admittedly- close enough,
but not identical, which is why I said
that RPM is retarded ;)

Cheers,
Tink

So does

/usr/lib/libssl.so.0.9.6 != libssl.so.0.9.6

That's the part I still don't get. Where do I get the correct libssl.so.0.9.6 then? I went to openssl.org and didn't see anything that I could use without having to compile myself which I am not quite ready for. Since MySQL 3.23 worked fine on this box, it seems odd that the new version would need older libraries than the older MySQL. No?

Thanks

Not in terms of RPM ... you can, however,
since you do have at least one version
that qualifies (wherever it came from, maybe
you installed a MDK rpm on your RH box
and they use different conventions for their
databases) you could always do a "--force"ed
install of MySQL and just ignore the warnings.

However, this is one of the reasons why I'm
using Slackware ;)

Cheers,
Tink

So, what is Slackware? I tried downloading Ximian Red Carpet, but it wanted an OLDER version of RPM that what comes with RH 9. So that wasn't a great idea. Hmm...

When I tried to do the force, it kept coming back with "Segmentation Fault". So, the force didn't seem to work.

Thanks

yes, I met this "Segmentation fault" too. Anyone know about this error?

Usually, seems like I see this when something has dependencies and the force just won't work. Saw the same problem with MySQL. Try without the --force and see what it is looking for.

you showed you have libssl.so.0.9.6 in /usr/lib, do you also have libcrypto.so.0.9.6 in /usr/lib?

If so I would submit that it's not in your lib path, which is not the same as your path

to fix it add /usr/lib to /etc/ld.so.conf

then run ldconfig


if /usr/lib is already there run ldconfig.

if that does not help you need to get the right files installed, and I would be very surprised.