DAY 4...I'm a little frustrated being so close AND so far away.
However, the
Bitcoin Mayor of Las Vegas, Tuxavant, summed up my feelings nicely in this thread
https://bitcointalk.org/index.php?topic=85228.msg939240Even so, this will prove to be a very enlightening and educational experience for me as I've wanted to help maintain other packages too. This ECDSA thing has motivate me to finally learn how this stuff works.
I've already learned more about packages and source RPMs than what I thought I would have to

Amazingly, this is a classic problem according to Kano, who has been running Linux for 16 years.
Since there really is no one who has written this, that is easy to find on the net, for the last 7+ years this issue has existed ...
Note to self and others: "that is easy to find on the net" I'm trying to remember the search terms I originally typed in to find this information. I think it was some text from the build error during the compile.
If you remember what you typed to get here, please add a comment with the text "My Search Terms" somewhere prominent.Below is Kano's instructions repeated. It's for Fedora Core 16 though. I'm going to analyze and annotate them with what I've read so far.
I suspect one of the key reasons he was successful was because he did everything as root.
The CentOS instructions explicitly say that's living dangerously.
From the "Yum and RPM Tricks" at
http://wiki.centos.org/TipsAndTricks/YumAndRPM14. Get set up for rebuilding packages as yourself, not root
Sometimes you just have to rebuild that package - maybe only to use some configuration option which just isn't there in the official package. Or because you have found some great package which you really cannot find in the repositories, but the site only gives you RPMs for another distribution. So you have to grab the src.rpm and rebuild it for yourself. But you really do not want to do it as root. So here's how to rebuild your packages in your home directory - with your own user account.
With that warning in mind, Kano's Instructions from
https://bitcointalk.org/index.php?topic=85228.msg946289#msg946289Build openssl-1.0.0j with EC on fc16
------------------------------------
All this is run from root.
1) Find the correct SRC RPM
Update fc16 to the latest everything and get
openssl-1.0.0j-1.fc16.src.rpm
from any mirror
or later if there is a later version
(this was written 7-Jun-2012)
N.B. these details are specific for openssl-1.0.0j
but most developers should be able to adapt this to later versions
2) rpm -Uvh openssl-1.0.0j-1.fc16.src.rpm
3) cd ~/rpmbuild/SPECS
4) vim openssl.spec
look for "./Configure" at the start of a line
(in 1.0.0j-1.fc16 it is line 219)
about 3 lines down from that you will see:
enable-cms enable-md2 no-idea no-mdc2 no-rc5 no-ec no-ecdh no-ecdsa \
change it to look like:
enable-cms enable-md2 no-idea no-mdc2 no-rc5 enable-ec enable-ecdh enable-ecdsa \
search for
Source1: hobble-openssl
(line 29) and change it (comment it out) to:
#Source1: hobble-openssl
search for
%{SOURCE1} > /dev/null
(line 133) and change it (comment it out) to:
#%{SOURCE1} > /dev/null
go back to the top and increase "Release:"
line 24 increment the "Release:" number
e.g. change
Release: 1%{?dist}
to
Release: 2%{?dist}
5) install rpm-build
yum install rpm-build
6) cd ~/rpmbuild/SOURCES/
in ~/rpmbuild/SOURCES/ there is a file called "openssl-1.0.0j-usa.tar.xz"
rename it to "openssl-1.0.0j-usa.tar.xz.orig" (or whatever else you like)
get a full replacement for the tar file, at http://www.openssl.org/source/
http://www.openssl.org/source/openssl-1.0.0j.tar.gz
and put it in the directory: ~/rpmbuild/SOURCES/
then rename it to "openssl-1.0.0j-usa.tar.xz"
7) cd ~/rpmbuild/SPECS
rpmbuild -bb openssl.spec
8) You now have the RPM files you need in ~/rpmbuild/RPMS/*/
I'll start annotating in the next post.