StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSqlite3 error message
text
Body
copied!<p>Hey, I've recently been having trouble properly installing my Sqlite3 gem. I've already tried installing sqlite3, followed by sqlite3-ruby and I keep getting an error message. Can anyone tell me what I need to do to correct this? Here's the error message:</p> <pre><code>demetriuford$ gem install sqlite3-ruby 1.3.3 Building native extensions. This could take a while... ERROR: Error installing sqlite3-ruby: ERROR: Failed to build gem native extension. /Users/demetriuford/.rvm/rubies/ruby-1.9.2-head/bin/ruby extconf.rb checking for sqlite3.h... yes checking for sqlite3_libversion_number() in -lsqlite3... yes checking for rb_proc_arity()... yes checking for sqlite3_initialize()... no sqlite3-ruby only supports sqlite3 versions 3.6.16+, please upgrade! *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/Users/demetriuford/.rvm/rubies/ruby-1.9.2-head/bin/ruby --with-sqlite3-dir --without-sqlite3-dir --with-sqlite3-include --without-sqlite3-include=${sqlite3-dir}/include --with-sqlite3-lib --without-sqlite3-lib=${sqlite3-dir}/lib --with-sqlite3lib --without-sqlite3lib Gem files will remain installed in /Users/demetriuford/.rvm/gems/ruby-1.9.2-head/gems/sqlite3-1.3.3 for inspection. Results logged to /Users/demetriuford/.rvm/gems/ruby-1.9.2-head/gems/sqlite3-1.3.3/ext/sqlite3/gem_make.out ERROR: Could not find a valid gem '1.3.3' (>= 0) in any repository </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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