Robert,
Thanks very much for trying it out. I’d be ecstatic if it would just
work with Ruby 1.6 – I have no need of 1.8 features as yet!
I do have CygWin installed, so I’ll try your method as well.
Al
···
-----Original Message-----
From: Robert Feldt
Sent: Mon 5/19/2003 9:59 PM
To: ruby-talk ML
Subject: Re: Exerb and socket
On Tue, 20 May 2003, Albert Chou wrote:
It’s the socket.so shipped with the PragProg installer, which I
presume
is VC++ MSWin32. I don’t know what my Exerb cores were compiled with,
I’m using the ones I downloaded from the author’s site.
It should work but I had problems doing it that way so for exerb I
now build Ruby on cygwin but with the no-cygwin switch (ie mingw32) and
then install extensions etc (so they also are built with no-cygwin
switch)
then install exerb and run it => works every time.
Also the exerb authors can be somewhat slow to respond but I think its
mostly because of language barriers. So be patient.
I tried a simple test but it seems there are problems:
$ ruby -v
ruby 1.8.0 (2003-05-20) [i386-mingw32]
feldt@klabada /tmp
$ cat s.rb
require ‘socket’
feldt@klabada /tmp
$ ruby -r exerb/mkrbc s.rb
feldt@klabada /tmp
$ exerb.rb -c cui18z s.rbc
feldt@klabada /tmp
$ ls -al s.exe
-rwx------+ 1 root None 260729 May 20 06:50 s.exe
feldt@klabada /tmp
$ ./s.exe
s.rb:1: warning: Object#type is deprecated; use Object#class
s.rb:1:in `require’: Fail to call LoadLibraryEx function – Error.127
(LoadError
)
from s.rb:1
Before the error message I get an error message in message box that says
it can’t locate the rb_check_safe_obj procedure entry point in s.exe.
I checked the ruby sources used to build the 180.rbx’es for exerb and
the rb_check_safe_obj func is not in there => exerb 180 rbx’es are not
up-to-date with latest ruby 180.
Regards,
Robert