<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: RubyGems: With power comes responsibility</title>
	<atom:link href="http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/</link>
	<description>Compartiendo fragmentos de código con el mundo.</description>
	<lastBuildDate>Sun, 07 Mar 2010 15:27:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Guido</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-1008</link>
		<dc:creator>Guido</dc:creator>
		<pubDate>Fri, 26 Jun 2009 06:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-1008</guid>
		<description>A step-by-step guide like that would be awesome, and well worth a wait indeed :) Thanks a lot for all your answers!</description>
		<content:encoded><![CDATA[<p>A step-by-step guide like that would be awesome, and well worth a wait indeed <img src='http://blog.mmediasys.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Thanks a lot for all your answers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-1005</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Thu, 25 Jun 2009 22:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-1005</guid>
		<description>@Guido:

I know must be itching right now, but if you give me a couple of days to put a step by step guide everybody would benefit.

Basically the mysql gem available would not work, it broken for 1.9, so you need to use my project at GitHub.

On the Mongrel side, there are lot of things that need improvement over there.</description>
		<content:encoded><![CDATA[<p>@Guido:</p>
<p>I know must be itching right now, but if you give me a couple of days to put a step by step guide everybody would benefit.</p>
<p>Basically the mysql gem available would not work, it broken for 1.9, so you need to use my project at GitHub.</p>
<p>On the Mongrel side, there are lot of things that need improvement over there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guido</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-994</link>
		<dc:creator>Guido</dc:creator>
		<pubDate>Thu, 25 Jun 2009 09:18:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-994</guid>
		<description>I did read all your comments, I guess it&#039;s one of those common things where something that&#039;s very basic to you and everybody else who is used to compiling stuff on Windows but alien to me is not made explicit. Is there a way I can easily tell whether a gem is precompiled or not?

I only have Ruby 1.9 in the path - I put 1.8 in there only for a few minutes, for testing whether mysql works with 1.8. It did, so you&#039;re certainly right about me getting an 1.8 precompiled version. I&#039;ll look into this again. Currently extconf.rb fails, not finding mysql_query() in -lmysqlclient, eventhough I do have libmySQL.dll available through the path. I don&#039;t seem to be the only one with that problem though, I&#039;m sure I&#039;ll find a solution soon.

&lt;pre&gt;gem install mongrel --platform=ruby&lt;/pre&gt; doesn&#039;t seem to work either, it gives me the error &quot;http11.c:77: error: structure has no member named `ptr&#039;&quot;:

http://www.haslo.ch/temp-pics/Ruby-Nocompile.jpg

It seems that the version of the gem I got doesn&#039;t have these fixes here:
http://rubyforge.org/pipermail/mongrel-users/2008-April/005278.html - and if I attempt to change the C file by hand and then gem install again, the file reverts to its previous version, probably because of the package system?</description>
		<content:encoded><![CDATA[<p>I did read all your comments, I guess it&#8217;s one of those common things where something that&#8217;s very basic to you and everybody else who is used to compiling stuff on Windows but alien to me is not made explicit. Is there a way I can easily tell whether a gem is precompiled or not?</p>
<p>I only have Ruby 1.9 in the path &#8211; I put 1.8 in there only for a few minutes, for testing whether mysql works with 1.8. It did, so you&#8217;re certainly right about me getting an 1.8 precompiled version. I&#8217;ll look into this again. Currently extconf.rb fails, not finding mysql_query() in -lmysqlclient, eventhough I do have libmySQL.dll available through the path. I don&#8217;t seem to be the only one with that problem though, I&#8217;m sure I&#8217;ll find a solution soon.</p>
<pre>gem install mongrel --platform=ruby</pre>
<p> doesn&#8217;t seem to work either, it gives me the error &#8220;http11.c:77: error: structure has no member named `ptr&#8217;&#8221;:</p>
<p><a href="http://www.haslo.ch/temp-pics/Ruby-Nocompile.jpg" rel="nofollow">http://www.haslo.ch/temp-pics/Ruby-Nocompile.jpg</a></p>
<p>It seems that the version of the gem I got doesn&#8217;t have these fixes here:<br />
<a href="http://rubyforge.org/pipermail/mongrel-users/2008-April/005278.html" rel="nofollow">http://rubyforge.org/pipermail/mongrel-users/2008-April/005278.html</a> &#8211; and if I attempt to change the C file by hand and then gem install again, the file reverts to its previous version, probably because of the package system?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-991</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Thu, 25 Jun 2009 04:44:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-991</guid>
		<description>@Guido: it seems you didn&#039;t read my comments. so I&#039;m going to explain once again.

You installed the binary of mongrel for mingw32 platform, but for the wrong version of ruby.

The binary of Mongrel was built for 1.8 version of Ruby, not for 1.9!

You need to remove the binary gem and install the one labeled as &quot;ruby&quot;, so:

@gem install mongrel --platform=ruby@ should do the trick.

Anyhow, as I mentioned here, 1.1.5 gem got released but I&#039;m not 100% sure it got all the MinGW fixes in.

regarding MySQL, you&#039;re facing the exact same problem I mentioned before: running compiled extension for 1.8 against 1.9, that is not going to work.

I believe that is happening because you have both 1.9 and 1.8 on your PATH environment.

I know is hard to follow and understand all those little details, but this is exactly the same under any kind of operating system.</description>
		<content:encoded><![CDATA[<p>@Guido: it seems you didn&#8217;t read my comments. so I&#8217;m going to explain once again.</p>
<p>You installed the binary of mongrel for mingw32 platform, but for the wrong version of ruby.</p>
<p>The binary of Mongrel was built for 1.8 version of Ruby, not for 1.9!</p>
<p>You need to remove the binary gem and install the one labeled as &#8220;ruby&#8221;, so:</p>
<p><code>gem install mongrel --platform=ruby</code> should do the trick.</p>
<p>Anyhow, as I mentioned here, 1.1.5 gem got released but I&#8217;m not 100% sure it got all the MinGW fixes in.</p>
<p>regarding MySQL, you&#8217;re facing the exact same problem I mentioned before: running compiled extension for 1.8 against 1.9, that is not going to work.</p>
<p>I believe that is happening because you have both 1.9 and 1.8 on your <span class="caps">PATH </span>environment.</p>
<p>I know is hard to follow and understand all those little details, but this is exactly the same under any kind of operating system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guido</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-987</link>
		<dc:creator>Guido</dc:creator>
		<pubDate>Wed, 24 Jun 2009 18:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-987</guid>
		<description>I think I&#039;ll go and see if I find a mysql-specific mailing list, and ask there :) There&#039;s bound to have been somebody else with the same problem.</description>
		<content:encoded><![CDATA[<p>I think I&#8217;ll go and see if I find a mysql-specific mailing list, and ask there <img src='http://blog.mmediasys.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  There&#8217;s bound to have been somebody else with the same problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guido</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-983</link>
		<dc:creator>Guido</dc:creator>
		<pubDate>Wed, 24 Jun 2009 16:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-983</guid>
		<description>Thanks for linking me here from that other post. I seem to have a problem with the mingw32 version of the mongrel gem as well though:

D:\Rails\testproject&gt;ruby script/server
F:/Ruby/lib/ruby/gems/1.9.1/gems/mongrel-1.1.5-x86-mingw32/lib/http11.so: [BUG] Segmentation fault
ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mingw32]

-- control frame ----------
c:0019 p:-14382694 s:0073 b:0073 l:000072 d:000072 TOP
c:0018 p:---- s:0071 b:0071 l:000070 d:000070 CFUNC  :require
c:0017 p:0012 s:0067 b:0067 l:000056 d:000066 BLOCK  F:/Ruby/lib/ruby/gems/1.9.1/gems/activesupport-2.3.2/lib/active_support/dependencies.rb:156

Any idea what I&#039;m doing wrong? (And huge thanks for your help!)
(Concerning MySQL, 5.0 didn&#039;t work for me either :( - I installed the 5.0 essentials, ran the service, even made the database, and rake db:migrate would produce exactly the same segfault error as it did with 5.1)</description>
		<content:encoded><![CDATA[<p>Thanks for linking me here from that other post. I seem to have a problem with the mingw32 version of the mongrel gem as well though:</p>
<p>D:\Rails\testproject&gt;ruby script/server<br />
F:/Ruby/lib/ruby/gems/1.9.1/gems/mongrel-1.1.5-x86-mingw32/lib/http11.so: [BUG] Segmentation fault<br />
ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mingw32]</p>
<p>&#8211; control frame &#8212;&#8212;&#8212;-<br />
c:0019 p:-14382694 s:0073 b:0073 l:000072 d:000072 <span class="caps">TOP</span><br />
c:0018 p:&#8212;- s:0071 b:0071 l:000070 d:000070 <span class="caps">CFUNC  </span>:require<br />
c:0017 p:0012 s:0067 b:0067 l:000056 d:000066 <span class="caps">BLOCK </span> F:/Ruby/lib/ruby/gems/1.9.1/gems/activesupport-2.3.2/lib/active_support/dependencies.rb:156</p>
<p>Any idea what I&#8217;m doing wrong? (And huge thanks for your help!)<br />
(Concerning MySQL, 5.0 didn&#8217;t work for me either <img src='http://blog.mmediasys.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  &#8211; I installed the 5.0 essentials, ran the service, even made the database, and rake db:migrate would produce exactly the same segfault error as it did with 5.1)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recent Links Tagged With "rubygems" - JabberTags</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-260</link>
		<dc:creator>Recent Links Tagged With "rubygems" - JabberTags</dc:creator>
		<pubDate>Mon, 27 Oct 2008 22:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-260</guid>
		<description>[...] public links &gt;&gt; rubygems   DEV_MEM.dump_to(:blog) :: RubyGems: With power comes responsibility Saved by jagayx on Sun 26-10-2008   rubygems: updating to 1.2.0 Saved by buroku on Thu 23-10-2008   [...]</description>
		<content:encoded><![CDATA[<p>[...] public links &gt;&gt; rubygems   <span class="caps">DEV</span>_MEM.dump_to(:blog) :: RubyGems: With power comes responsibility Saved by jagayx on Sun 26-10-2008   rubygems: updating to 1.2.0 Saved by buroku on Thu 23-10-2008   [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roger</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-205</link>
		<dc:creator>roger</dc:creator>
		<pubDate>Tue, 26 Aug 2008 15:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-205</guid>
		<description>Yeah really what you should do for gems that don&#039;t compile is not force but  figure out why and alert the author.  IMO the ideal is just for gems to all compile out of the box for mingw, but that&#039;s just me :)
[mongrel does...others can too]</description>
		<content:encoded><![CDATA[<p>Yeah really what you should do for gems that don&#8217;t compile is not force but  figure out why and alert the author.  <span class="caps">IMO </span>the ideal is just for gems to all compile out of the box for mingw, but that&#8217;s just me <img src='http://blog.mmediasys.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> <br />
[mongrel does...others can too]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nome do Jogo &#187; Artigo &#187; Rails Podcast Brasil - Episódio 27</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-199</link>
		<dc:creator>Nome do Jogo &#187; Artigo &#187; Rails Podcast Brasil - Episódio 27</dc:creator>
		<pubDate>Thu, 14 Aug 2008 14:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-199</guid>
		<description>[...] RubyGems: With power comes responsibility [...]</description>
		<content:encoded><![CDATA[<p>[...] RubyGems: With power comes responsibility [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/comment-page-1/#comment-195</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Mon, 11 Aug 2008 10:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mmediasys.com/?p=43#comment-195</guid>
		<description>Yeah Fabio, the thing is that not all the gems have this problems with mswin32 / mingw32.

I&#039;ll try to write a post as tutorial for people to contribute and spot those issues, but dunno if that will help.</description>
		<content:encoded><![CDATA[<p>Yeah Fabio, the thing is that not all the gems have this problems with mswin32 / mingw32.</p>
<p>I&#8217;ll try to write a post as tutorial for people to contribute and spot those issues, but dunno if that will help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
