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

**URL:** <https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839>\
**Category:** wxRuby\
**Created:** [May 26, 2009, 4:22pm UTC](https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839 "2009-05-26T16:22:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![quintus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/q/49beb7/32.png) [@quintus](https://www.ruby-forum.com/u/quintus)\
**Post date:** [May 26, 2009, 4:22pm UTC](https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839/1 "2009-05-26T16:22:25Z")

</div>

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](http://rubyinstaller.org/downloads/).

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

---

<div class="post-metadata">

**Author:** ![quintus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/q/49beb7/32.png) [@quintus](https://www.ruby-forum.com/u/quintus)\
**Post date:** [May 26, 2009, 8:15pm UTC](https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839/2 "2009-05-26T20:15:14Z")

</div>

Hi Marvin,

On Tue, May 26, 2009 at 4:22 PM, Marvin Gülker [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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](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.

---

<div class="post-metadata">

**Author:** ![quintus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/q/49beb7/32.png) [@quintus](https://www.ruby-forum.com/u/quintus)\
**Post date:** [May 27, 2009, 8:37pm UTC](https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839/3 "2009-05-27T20:37:23Z")

</div>

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… 🙂

Thanks!

Marvin

---

<div class="post-metadata">

**Author:** ![quintus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/q/49beb7/32.png) [@quintus](https://www.ruby-forum.com/u/quintus)\
**Post date:** [November 5, 2009, 6:26pm UTC](https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839/4 "2009-11-05T18:26:40Z")

</div>

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](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.

---

<div class="post-metadata">

**Author:** ![quintus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/q/49beb7/32.png) [@quintus](https://www.ruby-forum.com/u/quintus)\
**Post date:** [December 5, 2009, 9:21pm UTC](https://www.ruby-forum.com/t/unable-to-use-wxruby-ruby19-in-ruby-1-9-1-p129-on-windows/168839/5 "2009-12-05T21:21:36Z")

</div>

Dit it now myself. And worked : )
