Note that there are some explanatory texts on larger screens.

plurals
  1. POError setting up Ruby on Rails
    text
    copied!<p><a href="http://guides.rubyonrails.org/getting_started.html" rel="noreferrer">Following this guide</a>, I'm attempting to set up Ruby on Rails using Amazon's EC2. For my instance I've selected "Basic 32-bit Amazon Linux AMI 2010.11.1 Beta". I have ruby, sqlite, and rubygems installed. I'm on step 3.3 of the linked guide which is to run the following command</p> <blockquote> <p>bundle install</p> </blockquote> <p>The result is the following. I'm sure I've just missed something, but I'm at a loss. Any suggestions?</p> <pre><code>Installing sqlite3 (1.3.3) with native extensions /usr/lib/ruby/site_ruby/1.8/rubygems /installer.rb:529:in `build_extensions': ERROR: Failed to build gem native extension (Gem::Installer::ExtensionBuildError) /usr/bin/ruby extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/ruby.h Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/sqlite3-1.3.3 for inspection. </code></pre> <p><strong>EDIT</strong>: Following the suggestion below to install ruby-devel, I now get this error in addition to the original one.</p> <pre><code>Installing sqlite3 (1.3.3) with native extensions /usr/lib/ruby/site_ruby/1.8/rubygems/installer.rb:529:in `build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError) /usr/bin/ruby extconf.rb checking for sqlite3.h... no sqlite3.h is missing. Try 'port install sqlite3 +universal' or 'yum install sqlite3-devel' and check your shared library search path (the location where your sqlite3 shared library is located). </code></pre> <p>But when I try to run </p> <blockquote> <p>yum install sqlite-devel</p> </blockquote> <p>I'm told:</p> <pre><code>Package sqlite-devel-3.6.20-1.6.amzn1.i386 already installed and latest version Nothing to do </code></pre>
 

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