If anyone''s interested my fork has an option GCC43=1 to use GCC 43 instead of the default. http://github.com/rogerdpack/rubyinstaller/tree/master feel free to use or merge if useful. I originally tried also adding extra CFLAGS like "-march=native -O3" but the subsequent build broke [not sure which one caused it to do so]. Just building with GCC43=1 seems to work all right though. Cheers! -=r
I use Ruby 1.9.1 with minwg gcc 4.3.x a long time. It seems to be OK, only Eventmachine doesn''t work fine :(. My mingw32 is from this place: http://sourceforge.net/projects/tdm-gcc/ Dne 30.3.2009 15:43, Roger Pack napsal(a):> If anyone''s interested my fork has an option GCC43=1 to use GCC 43 > instead of the default. > http://github.com/rogerdpack/rubyinstaller/tree/master > feel free to use or merge if useful. > > I originally tried also adding extra CFLAGS like "-march=native -O3" > but the subsequent build broke [not sure which one caused it to do > so]. Just building with GCC43=1 seems to work all right though. > > Cheers! > -=r > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
On Mon, Mar 30, 2009 at 11:06 AM, deepj <deepjungle.maca at gmail.com> wrote:> I use Ruby 1.9.1 with minwg gcc 4.3.x a long time. It seems to be OK, only > Eventmachine doesn''t work fine :(. > > My mingw32 is from this place: > http://sourceforge.net/projects/tdm-gcc/Yeah that''s the one I linked to as an option :) How to reproduce the EM errror? -=r
On Mon, Mar 30, 2009 at 10:43 AM, Roger Pack <rogerdpack at gmail.com> wrote:> > If anyone''s interested my fork has an option GCC43=1 to use GCC 43 > instead of the default. > http://github.com/rogerdpack/rubyinstaller/tree/master > feel free to use or merge if useful. >Awesome work Roger!. Definitely I''m going to merge those into dsl branch.> I originally tried also adding extra CFLAGS like "-march=native -O3" > but the subsequent build broke [not sure which one caused it to do > so]. ?Just building with GCC43=1 seems to work all right though. >Yeah, native optimizations are not 100% working, tried that once and reverted to -O2. I''m going to work over the next few days on testing GCC4 and GCC 3.4.5 builds of Ruby. Trying to get mingw-w64 working too, had a Xeon at the office for a couple of days and looks like my migration to x64 should happen soon. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry
> Yeah, native optimizations are not 100% working, tried that once and > reverted to -O2. > > I''m going to work over the next few days on testing GCC4 and GCC 3.4.5 > builds of Ruby. > > Trying to get mingw-w64 working too, had a Xeon at the office for a > couple of days and looks like my migration to x64 should happen soon.Wow good luck with that one. :) -=r
> Yeah that''s the one I linked to as an option :) > How to reproduce the EM errror?You can run EventMachine tests using rake:test. When I run it EventMachine will stop responding (I must kill it). The compile seems to be fine, only a few warnings. Maybe the problem is in OpenSSL libraries. I''ve used OpenSSL 0.9.8j from this place http://www.slproweb.com/products/Win32OpenSSL.html (the full installation contains dev files for mingw) when I compiled Ruby 1.9.1. Can you try it and you can confirm it if the problem in this? I''m sorry for my ugly english :)
On Tue, Mar 31, 2009 at 5:47 PM, deepj <deepjungle.maca at gmail.com> wrote:>> Yeah that''s the one I linked to as an option :) >> How to reproduce the EM errror? > > You can run EventMachine tests using rake:test. When I run it EventMachine > will stop responding (I must kill it). The compile seems to be fine, only a > few warnings. > > Maybe the ?problem is in OpenSSL libraries. I''ve used OpenSSL 0.9.8j from > this place http://www.slproweb.com/products/Win32OpenSSL.html (the full > installation contains dev files for mingw) when I compiled Ruby 1.9.1. Can > you try it and you can confirm it if the problem in this? > > I''m sorry for my ugly english :)I believe that version of OpenSSL is linked with MSVCR80/90, not msvcrt, which is used by MinGW). Be careful using those binaries. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry
> Maybe the ?problem is in OpenSSL libraries. I''ve used OpenSSL 0.9.8j from > this place http://www.slproweb.com/products/Win32OpenSSL.html (the full > installation contains dev files for mingw) when I compiled Ruby 1.9.1. Can > you try it and you can confirm it if the problem in this? > > I''m sorry for my ugly english :)Sure I''ll try it out sometime. Might take me a little bit to get to it :) -=r
On Tue, Mar 31, 2009 at 6:54 PM, Roger Pack <rogerdpack at gmail.com> wrote:>> Maybe the ?problem is in OpenSSL libraries. I''ve used OpenSSL 0.9.8j from >> this place http://www.slproweb.com/products/Win32OpenSSL.html (the full >> installation contains dev files for mingw) when I compiled Ruby 1.9.1. Can >> you try it and you can confirm it if the problem in this? >> >> I''m sorry for my ugly english :) > > > Sure I''ll try it out sometime. ?Might take me a little bit to get to it :)What about proper-openssl branch? It builds it from source and do not depend on external binaries (so it can build latest version of OpenSSL). -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry
> What about proper-openssl branch? It builds it from source and do not > depend on external binaries (so it can build latest version of > OpenSSL). >I''ve compiled openssl-0.9.8h (+ openssl-0.9.8i -- higher versions are broken under mingw) using this today and the eventmachine has still got the issue with freezing.
> I use Ruby 1.9.1 with minwg gcc 4.3.x a long time. It seems to be OK, only > Eventmachine doesn''t work fine :(.I seem unable to get any version of windows ruby to run the EM tests. Not quite sure why. For sure when I build with GCC 3.4 they still don''t run, so it may not be 4.3''s fault :) -=r
On Tue, Apr 14, 2009 at 11:13 PM, Roger Pack <rogerdpack at gmail.com> wrote:>> I use Ruby 1.9.1 with minwg gcc 4.3.x a long time. It seems to be OK, only >> Eventmachine doesn''t work fine :(. > > I seem unable to get any version of windows ruby to run the EM tests. > Not quite sure why. ?For sure when I build with GCC 3.4 they still > don''t run, so it may not be 4.3''s fault :) >I still didn''t find a good reason (from my side) to tackle this task, either with GCC 3.4.5 or 4.3. Even more since there is no non-blocking interface built for Ruby 1.8 or 1.9 for Windows. MSI Installers for 1.8 and 1.9 are coming next week, and devkit gem to follow (spare time every weekend, no free time during work days). If you guys start posting concrete examples I can chime in and help out, that will be great. Cheers, -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry