i am trying to setup a slicehost server for rails development. i chose
to use the ubuntu 9.10 karmic image.
rvm looks really useful so i am attempting to use it.
i am running into trying to use sqlite3 with ruby 1.9.1.
here is what i have setup gist:333205 · GitHub.
everything seems to work great up to the sqlite3 part.
does anyone know how to get sqlite3 working with ruby 1.9.1 on ubuntu
9.10? i have tried many approaches found through google and nothing
has worked.
thanks,
scott
On Mon, Mar 15, 2010 at 2:40 PM, scott [email protected] wrote:
i am trying to setup a slicehost server for rails development. i chose
to use the ubuntu 9.10 karmic image.
rvm looks really useful so i am attempting to use it.
i am running into trying to use sqlite3 with ruby 1.9.1.
here is what i have setup gist:333205 · GitHub.
everything seems to work great up to the sqlite3 part.
make sure you don’t have both sqlite3 and sqlite3-ruby.
Those two modules can conflict.
Andrew McElroy
On Mar 15, 8:37 pm, scott [email protected] wrote:
i am trying to setup a slicehost server for rails development. i chose
to use the ubuntu 9.10 karmic image.
rvm looks really useful so i am attempting to use it.
i am running into trying to use sqlite3 with ruby 1.9.1.
here is what i have setuphttp://gist.github.com/333205.
everything seems to work great up to the sqlite3 part.
You put ???, what is supposed that means?
For the record: gem install sqlite3-ruby should install ruby as long
you have sqlite3-dev headers installed:
The package is “libsqlite3-dev”
does anyone know how to get sqlite3 working with ruby 1.9.1 on ubuntu
9.10? i have tried many approaches found through google and nothing
has worked.
If you installed “sqlite3” gem, let me tell you is an FFI
implementation, which is broken. I asked the gem author to change the
name to avoid confusion, but he rejected it.
HTH,
On Mon, Mar 15, 2010 at 2:43 PM, andrew mcelroy [email protected]
wrote:
make sure you don’t have both sqlite3 and sqlite3-ruby.
Those two modules can conflict.
Gems not modules.
i think my problem was having both sqlite3 and sqlite3-ruby installed
thanks for the tip!