[Rubyinstaller-devel] compiling OpenSSL
luislavena at gmail.com
Fri Apr 11 17:57:35 EDT 2008
On Fri, Apr 11, 2008 at 5:57 PM, Gordon Thiesfeld <gthiesfeld at gmail.com> wrote:
> On Thu, Apr 10, 2008 at 3:01 PM, Luis Lavena <luislavena at gmail.com> wrote:
> > Hello Gordon!
> > I wasn't aware there are OpenSSL failures in the MinGW build. AFAIK
> > the only blocker I still have is test_readline, which hangs and halt
> > the whole 'rake check' process.
> I'm running bzr revision 52. I get this on 'rake check'.
> ./ruby_1_8/test/openssl/test_hmac.rb:14: [BUG] Segmentation fault
> ruby 1.8.6 (2008-03-03) [i386-mingw32]
That segfault came from your OpenSSL change, or that is generated by
"out of the box" recipes?
Can you provide information about your Windows installation?
(XP/Vista, home, ultimate, service pack level, etc).
Also will be helpful know your PATH environment variable:
ECHO %PATH% (or SET PATH without params)
> This application has requested the Runtime to terminate it in an unusual way.
> Please contact the application's support team for more information.
> make: *** [test-all] Error 3
> rake aborted!
> Command failed with status (2): ["C:/ruby/repo/installer3/sandbox/msys/bin/...]
> (See full trace by running task with --trace)
> > Can you provide the output or the error message you're getting when it
> > tries to extract it?
> "C:/ruby/repo/oci/sandbox/extract_utils/bsdtar.exe" xzf
> openssl-0.9.8g/apps/md4.c: Can't create 'openssl-0.9.8g/apps/md4.c':
> No such file or directory
Ok, no doubt bsdtar cannot handle latest openssl packages. I'm
checking right now what version can and cannot be unpacked:
0.9.7l, 0.9.7m, 0.9.8d, 0.9.8e, 0.9.8f and 0.9.8g all fail in the same files:
openssl-0.9.7l/apps/md4.c: Can't create 'openssl-0.9.7l/apps/md4.c':
No such file or directory
openssl-0.9.7l/include/openssl/kssl.h: Can't create
'openssl-0.9.7l/include/openssl/kssl.h': No such file or directory
openssl-0.9.7l/include/openssl/ssl23.h: Can't create
'openssl-0.9.7l/include/openssl/ssl23.h': No such file or directory
openssl-0.9.7l/include/openssl/ssl2.h: Can't create
'openssl-0.9.7l/include/openssl/ssl2.h': No such file or directory
openssl-0.9.7l/include/openssl/ssl3.h: Can't create
'openssl-0.9.7l/include/openssl/ssl3.h': No such file or directory
openssl-0.9.7l/include/openssl/ssl.h: Can't create
'openssl-0.9.7l/include/openssl/ssl.h': No such file or directory
openssl-0.9.7l/include/openssl/tls1.h: Can't create
'openssl-0.9.7l/include/openssl/tls1.h': No such file or directory
openssl-0.9.7l/test/fips_aes_data: Can't create
'openssl-0.9.7l/test/fips_aes_data': No such file or directory
If OpenSSL cannot be extracted using simple tar, then bsdtar is not
enough or openssl packages are corrupt somehow.
> > Also, this OpenSSL need ot be extracted in it's
> > own directory, instead of using the OpenSSL package target location,
> > instead of MinGW one.
> Right, I had set it up with a similar folder structure to Ruby's
> (openssl, openssl_build, openssl_mingw).
> > Please do, I'll suggest you revert your changes, use latest.zip and
> > let rake do it's stuff, then use the sandbox/mingw and sandbox/msys as
> > base MinGW and start playing with manual build of OpenSSL.
> I did bzr revert, and I'm going to give this a try.
> > I'll hang out at #ruby-lang the weekend, trying to get other gems
> > working on Windows and MinGW.
> I'll try to stop by. I could use some help ;)
Good, me too ;-)
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
More information about the Rubyinstaller-devel