The PostgreSQL 8.3 release ships with its own ssleay32.dll. However,
when building with VC++ 6 using the one-click installer, I need to use
the ssleay32.dll that Curt ships under c:/ruby/bin.
I’ve been toying with $LDFLAGS and $LIBPATH but I can’t make it work. I
always get a “The ordinal 284 could not be located in the dynamic link
library SSLEAY32.DLL”.
What mkmf incantation must I perform to make it work?
At Sun, 10 Feb 2008 07:11:55 +0900,
Daniel B. wrote in [ruby-talk:290550]:
The PostgreSQL 8.3 release ships with its own ssleay32.dll. However,
when building with VC++ 6 using the one-click installer, I need to use
the ssleay32.dll that Curt ships under c:/ruby/bin.
I’ve been toying with $LDFLAGS and $LIBPATH but I can’t make it work. I
always get a “The ordinal 284 could not be located in the dynamic link
library SSLEAY32.DLL”.
Maybe, INCLUDE and LIB environment variables are set for
PostgreSQL?
Maybe, INCLUDE and LIB environment variables are set for
PostgreSQL?
I tried setting both LIB and LIBDIR to C:\ruby\bin, both in the shell
itself and via ENV, but it didn’t work.
Have you been able to build and load ruby-pg against PostgreSQL 8.3 with
the one click installer? If so, how did you do it?
Regards,
Dan
I have done a work-around by renaming the libeay32.dll and ssleay32.dll
in {RUBY_PATH}/bin directory and copy these to dll files from
{POSTGRES_PATH}/bin directory and paste it under {RUBY_PATH}/bin.
It worked for me.
My work-around worked in just the opposite way. Having boy files
libeay32.dll and ssleay32.dll in {POSTGRES_PATH}/bin directory and
nothing in {RUBY_PATH}/bin directory, finally did the trick, but I
noticed they had to have the same date.
Maybe, INCLUDE and LIB environment variables are set for
PostgreSQL?
I tried setting both LIB and LIBDIR to C:\ruby\bin, both in the shell
itself and via ENV, but it didn’t work.
Have you been able to build and load ruby-pg against PostgreSQL 8.3 with
the one click installer? If so, how did you do it?
Regards,
Dan
I have done a work-around by renaming the libeay32.dll and ssleay32.dll
in {RUBY_PATH}/bin directory and copy these to dll files from
{POSTGRES_PATH}/bin directory and paste it under {RUBY_PATH}/bin.
My work-around worked in just the opposite way. Having boy files
libeay32.dll and ssleay32.dll in {POSTGRES_PATH}/bin directory and
nothing in {RUBY_PATH}/bin directory, finally did the trick, but I
noticed they had to have the same date.
Please try RubyInstaller:
It includes OpenSSL in “compatibility mode” so it doesn’t conflict
with PostgreSQL.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.