C.R., just what compiled libraries does PayflowPro ship with? Because
I'm not sure, but you
might be able to de-link libpfpro.so
into object files with
ar -x and then re-link it to the
appropriate OpenSSL library with
ld. I'm know nothing
about PayflowPro, but in the past I've used ar -x to take apart .a
libraries and re-build them into a .so.
However, what is the real problem causing the segafaults here? Is it
that libpfpro.so (with OpenSSL 0.9.5 statically linked in) just isn't
thread safe, period? Or is some kind of version skew between the
OpenSSL 0.9.5 and 0.9.6c libraries? If libpfpro.so has OpenSSL 0.9.5
statically linked in, then why would it matter at all what other
version of OpenSSL you have installed on your machine?
