On 9/30/2011 5:04 PM, michael lush wrote:
On Fri, Sep 30, 2011 at 3:07 PM, Jakob Bohm<jb-open...@wisemo.com> wrote:
Short answer to subject: Yes.
If it is I'm pointing configure at the wrong place and I need to look
elsewhere :-)
Maybe. Maybe not. Look in your local install and make sure all of the
following is there:
A directory "include/openssl/" containing lots of header files
Linkable shared libraries "lib/libcrypto.so" and "lib/libssl.so" (.DLL if
Windows, OS/2 or Symbian).
Linkable static libraries "lib/libcrypto.a" and "lib/libssl.a" (.LIB if
Windows, OS/2 or Symbian).
Thanks for this its a real help! I've had a look at the installation
and there is "lib/libcrypto.a"
but no "lib/libcrypto.so" I'll have another look at how in installed it.
Ok, this means you compiled openssl as static libraries to be linked
into you postgres programs.
To get the .so variant, compile openssl as dynamic libraries (DLLs).
To get both types you typically need to compile openssl twice, because
on Linux, code that goes in DLLs is typically compiled as
"Position Independent Code" which code for a program file is not. The
.a file is typically compiled for inclusion in a program.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
