Hello,
I am new to rvm, However I have never had this sort of issue.
My OS was Debian Lenny old-stable so that made me to migrate to Debian Wheezy x86_64 (stable).
gcc 4.4.7-2
git 1.8.1.2
curl 7.21.0
bash 4.1.5
After installing all the dependencies ruby needs I installed rvm:
So far so good, However when I tried to install ruby 2.0
rvm install ruby-2.0.0
Despite the fact it is not being compiled the installation finished without prompting any error, Therefore when I run:
rvm 2.0.0
ruby -v
It says:
$HOME/.rvm/rubies/ruby-2.0.0-p195/bin/ruby: No such file or directory
As it shows, somehow it is not being compiled, Now I don't know how the lastest rvm works when installing ruby.
Therefore I started looking for the 'cure'
What I came up with was:
rvm install ruby-2.0.0 --with-gcc=gcc
When I do this it does compile and works perfectly.
Thereafter when I run:
rvm 2.0
ruby -v #=> ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]
It does not shows the error:
$HOME/.rvm/rubies/ruby-2.0.0-p195/bin/ruby: No such file or directory
Okay it is working, but I am so curious why it works that I need to ask the ones more skilled than me.
Due to some hacking in the expectation of getting it to work, I have seen that when I type rvm install 2.0, it downloads ruby-2.0.0-p195.tar.bz2 and it renames it prepending 'bin'.
When I type rvm install 2.0 --with-gcc=gcc which downloads ruby-2.0.0-p195.tar.bz2 and does not prepend bin to its file's name.
Moreover, I installed ruby 1.8.7 and it worked perfectly, without using any flag.
What I have also noticed is that bin-ruby-2.0.0-p195 has a dir tree totally different than ruby-2.0.0-p195 .
Also rvm install 2.0.0 does not generate any blob_number_extract.log, _name.log, _install.log. However it generates blob_number_gem.install.log, _gemsets.initial.log, etc.
Whereas rvm install 2.0.0 --with-gcc=gcc generates all sorts of logs.
I am looking forward to hearing from you.
Kind Regards,
Antonio C Nalesso