Comments on: Uninitialized Constant GemRunner Error When Using Ruby Gem

By: Henning

Henning — Tue, 29 Jul 2008 12:42:25 +0000

Thank you very much for the hint.

By: Rails con Postgres « El Reino del Terror - Tecnología y otros Tormentos…

Mon, 28 Apr 2008 18:45:07 +0000

[...] Tras “googlear” un rato encontré esta solución: http://www.theirishpenguin.com/2007/12/09/uninitialized-constant-gemrunner-error-when-using-ruby-gem... [...]

By: TLJ

TLJ — Sun, 06 Jan 2008 00:49:43 +0000

Thank you!!

By: Frederik Braun

Frederik Braun — Fri, 28 Dec 2007 19:35:03 +0000

Wow, that was *really* helpful.
Greetings from Germany, and thank you

Frederik

By: Fred

Fred — Sat, 22 Dec 2007 16:15:33 +0000

Thanks, removing the stray site_ruby directory was the solution I needed. The problem started for me when I tried to update rubygems by running gem update system instead of going through apt-get. Goes to show that a language or framework choice has to include a choice of everything underneath it in the stack: you never just run rails, you run rails sitting on top of gems sitting on top of apt-got packages and maybe some make-installed packages to plug the gaps.

By: theirishpenguin

theirishpenguin — Sat, 08 Dec 2007 22:44:19 +0000

Just a quick note, the next problem we had was installing the fast debugger, which we wanted to use with a nightly build of Netbeans. The error was …

ERROR: Error installing ruby-debug-ide:
ERROR: Failed to build gem native extension.

…followed by errors like…

ruby_debug.c:1:19: error: stdio.h: No such file or directory
In file included from ruby_debug.c:2:
/usr/lib/ruby/1.8/i486-linux/ruby.h:40:21: error: stdlib.h: No such file or directory
/usr/lib/ruby/1.8/i486-linux/ruby.h:44:21: error: string.h: No such file or directory
/usr/lib/ruby/1.8/i486-linux/ruby.h:71:20: error: alloca.h: No such file or directory

… as it was obvious that these were C/C++ style errors the answer was to install the build-essential package with

sudo apt-get build-essential