'rails c' command throws back error

Hi,

I am new to ruby and rails. I have been working through a few tutorials
etc
trying to get up to speed.

However I have run into one issue I’m unsure how to go about solving. I
am
using RVM to manage my ruby verions. By default I have 1.8.7 installed
on
my system(Ubuntu man, but I am on Linux Mint Maya).

With my latest project however I am using 1.9.3(with rails 3.2.11).
Everything works great and I very happy, but when I try run “rails c” or
“rails console” I get the following error…

“”"
/home/phil/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/irb/completion.rb:9:in
require': cannot load such file -- readline (LoadError) from /home/phil/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/irb/completion.rb:9:in<top (required)>’
from
/home/phil/.rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.11/lib/rails/commands/console.rb:3:in
require' from /home/phil/.rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.11/lib/rails/commands/console.rb:3:in<top (required)>’
from
/home/phil/.rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.11/lib/rails/commands.rb:38:in
require' from /home/phil/.rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.11/lib/rails/commands.rb:38:in<top (required)>’
from script/rails:6:in require' from script/rails:6:in
“”"

So as a result I am unable to use the console at all on this project. If
anybody had any clue on how to solve this I would be most grateful!

ps when I run “rvm use 1.9.3” it returns…

Using /home/phil/.rvm/gems/ruby-1.9.3-p392

On Ubuntu you need libreadline6 and libreadline6-dev, though I don’t
know whether that is the same on mint. You might need to remove and
re-install ruby in rvm after installing libreadline so that it
re-compiles with the right options. The full list of stuff I install
before installing rvm is
sudo apt-get install build-essential bison openssl libreadline6
libreadline6-dev curl git-core
zlib1g zlib1g-dev libssl-dev libyaml-dev libxml2-dev autoconf
libc6-dev ncurses-dev automake
libtool

By the way, when you get an error you don’t understand often the best
route is to put the error message into google. I think that would
have taken you to a solution very quickly.

Colin