Unable to use wxruby-ruby19 in Ruby 1.9.1-p129 on Windows

Desktop wxRuby
1

Hello,

I’m using wxRuby as my favourite GUI toolkit with Ruby 1.9. But after I
updated my Ruby installation from Ruby 1.9.1-p0 to Ruby 1.9.1-p129, I
cannot do a require “wx” anymore. Every time I try I get an error that
says that Windows isn’t able to find some procedure. I have a German
Windows XP installation, so I don’t know the English equivalent of this
error (sorry):

irb(main):001:0> require “rubygems”
=> false
irb(main):002:0> require “wx”
LoadError: 127: Die angegebene Prozedur wurde nicht gefunden. -
C:/ruby19/ruby
-1.9.1-p129-i386-mingw32/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.0-x86-mingw3
2/lib/wxruby2.so
from
C:/ruby19/ruby-1.9.1-p129-i386-mingw32/lib/ruby/gems/1.9.1/gems/wxr
uby-ruby19-2.0.0-x86-mingw32/lib/wx.rb:12:in require' from C:/ruby19/ruby-1.9.1-p129-i386-mingw32/lib/ruby/gems/1.9.1/gems/wxr uby-ruby19-2.0.0-x86-mingw32/lib/wx.rb:12:in <top (required)>’
from (irb):2:in require' from (irb):2 from C:/ruby19/ruby-1.9.1-p129-i386-mingw32/bin/irb:12:in ’

I would translate it this way: “The given procedure wasn’t found”. At
the same time I get a Windows error window, saying:

Der Prozedureinsprungpunkt “DLLMain@12” wurde in der DLL
“msvcrt-ruby191.dll” nicht gefunden.

I don’t know how to translate “Prozedureinsprungpunkt”, but it must be
something like “procedure definition point”, so I would say:

The procedure definition point “DLLMain@12” wasn’t found in the
“msvcrt-ruby19.dll” DLL file.

I’m using the mingw version of ruby from
Downloads.

My full ruby -v:
ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mingw32]

2

Hi Marvin,

On Tue, May 26, 2009 at 4:22 PM, Marvin Gülker [email protected] wrote:

Hello,

I’m using wxRuby as my favourite GUI toolkit with Ruby 1.9. But after I
updated my Ruby installation from Ruby 1.9.1-p0 to Ruby 1.9.1-p129, I
cannot do a require “wx” anymore. Every time I try I get an error that
says that Windows isn’t able to find some procedure.

I had exactly the same problem when I upgraded my MinGW ruby-1.9.1
from p0 to p129.

I suspected a general binary incompatibility between these two
versions of ruby (see
http://rubyforge.org/pipermail/wxruby-users/2009-May/004862.html). But
this seems to be specific to MinGW.

The solution is to rebuild wxRuby-2.0 for the ruby-1.9.1-p129.

If you can’t rebuild the gem yourself, please wait for the upcoming
wxRuby-2.0.1 release.
The MinGW wxRuby-2.0.1 gem will be built for ruby-1.9.1-p129.

Cheers.

Chauk-Mean.

3

Chauk-Mean P. wrote:

The solution is to rebuild wxRuby-2.0 for the ruby-1.9.1-p129.

If you can’t rebuild the gem yourself, please wait for the upcoming
wxRuby-2.0.1 release.
The MinGW wxRuby-2.0.1 gem will be built for ruby-1.9.1-p129.
OK, so I’m going to wait for that release. I thought, I made something
wrong with updating my Ruby installation… :slight_smile:

Thanks!

Marvin

4

Chauk-Mean P. wrote:

this seems to be specific to MinGW.

The solution is to rebuild wxRuby-2.0 for the ruby-1.9.1-p129.

I just had this problem on OS X Leopard. Currently installing wxRuby
using “gem install wxruby” won’t work with a ruby19 system. As per the
gems listed on the rubyforge page
(http://rubyforge.org/frs/?group_id=35) I had to install the gem named
with ruby19:

gem uninstall wxruby
gem install wxruby-ruby19

After this the system worked as expected.

Dean.

5

Dit it now myself. And worked : )