Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat would cause native gem extensions on OS X to build but fail to load?
    primarykey
    data
    text
    <p>I am having trouble with some of my rubygems, in particular those that use native extensions.</p> <p>I am on a MacBookPro, with Snow Leopard. I have XCode 3.2.1 installed, with gcc 4.2.1. Ruby 1.8.6, because I'm lazy and a scaredy cat and don't want to upgrade yet. Ruby is running in 32-bit mode. I built this ruby from scratch when my MBP ran OSX 10.4.</p> <p>When I require one of the affected gems in irb, I get a Load Error for the gem extension's bundle file. For example, here's nokogigi dissing me:</p> <blockquote> <p>&gt; require 'rubygems'<br> => true<br> &gt; require 'nokogiri'<br> LoadError: Failed to load /usr/local/lib/ruby/gems/1.8/gems/nokogiri-1.4.1/lib/nokogiri/nokogiri.bundle</p> </blockquote> <p>This is also happening with the Postgres pg and MongoDB mongo gems.</p> <p>My first thought was that the extensions must not be building right. But gem install wasn't throwing any errors. So I reinstalled with the verbose flag, hoping to see some helpful warnings. <a href="http://pastie.org/895447" rel="nofollow noreferrer">I've put the output in a Pastie</a>, and the only warning I see is a consistent one about "passing argument n of ‘foo’ with different width due to prototype."</p> <p>I suspect that this might be an issue from upgrading to Snow Leopard, but I'm a little surprised to experience it now, since I've updated my XCode. Could it stem from running Ruby in 1.8.6? I'm embarrassed that I don't know quite enough about my Mac and OSX to know where to look next, so any guidance, even just a pointer to some document I couldn't find via Google, would be most welcome. </p> <p>Michael</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload