[KLUG Members] Redhat7.1 libcrypto

[Bryan-TheBS-Smith]

Jim Pharis wrote:
> OK. I fudged it with the src rpms.

Actually, you didn't "fudge it," you did it _exactly_ like one
should when you have library problems.  Read on ...

> I can't figure out what the difference is but this is how I did it.
> I just did a rpm --rebuild ./python.src.rpm  and it put all the rpms in
> /usr/src/redhat/rpms/i386/ and then rpm -Uhv ./python and it worked.
> Im still interested to know what was wrong??????

The binary RPMs were expecting newer releases of libcrypto.  RedHat
separates the newer 0.9.6 release from the older 0.9.5[a] release. 
I don't know if SuSE does the same.

So when you rebuild from the source code, the GNU Autoconf/make
utilities realized this.  So they build against just the older
libcrypto (or does SuSE not distinguish?).  Once that was done, you
were cooked!

It's _always_ good to rebuild from SRPM when you are trying to use
packages from other distros, or different major versions (e.g.,
rebuilding newer packages from RedHat 7.x on 6.x, etc...).

Be _glad_ that RPM _prevents_ you from installing something that you
don't have like the system the binary was built on.  Windows
doesn't, and that explains 50% of its crashes right off-the-bat!

-- TheBS

-- 
Bryan "TheBS" Smith     mailto:b.j.smith@ieee.org    chat:thebs413
Engineer   AbsoluteValue Systems, Inc.   http://www.linux-wlan.org
President    SmithConcepts, Inc.      http://www.SmithConcepts.com
------------------------------------------------------------------
Those living in the US who consider the American flag to be a sym-
bol of oppression obviously fail to understand what the word means