Running OSX ML 10.8.2 with Homebrew
(gps ~)$ rvm install ruby-1.9.3-p374
Requirements for osx/10.8/x86_64
NOTE: 'ruby' represents Matz's Ruby Interpreter (MRI) (1.8.X, 1.9.X)
This is the original / standard Ruby Language Interpreter
'ree' represents Ruby Enterprise Edition
'rbx' represents Rubinius
Error: Already tapped!
Error: bash-4.2.42 already installed
Error: curl-7.28.1 already installed
Error: git-126.96.36.199 already installed
Error: autoconf-2.69 already installed
Error: automake-1.13.1 already installed
Error: apple-gcc42-4.2.1-5666.3 already installed
Error: libtool-2.4.2 already installed
Error: pkg-config-0.27.1 already installed
Error: openssl-1.0.1c already installed
Error: readline-6.2.4 already installed
Error: libyaml-0.1.4 already installed
Error: sqlite-188.8.131.52 already installed
Error: libxml2-2.8.0 already installed
Error: libxslt-1.1.28 already installed
Error: libksba-1.3.0 already installed
Searching for binary rubies, this might take some time.
No binary rubies available for: osx/10.8/x86_64/ruby-1.9.3-p374.
Continuing with compilation. Please read 'rvm mount' to get more information on binary rubies.
Fetching yaml-0.1.4.tar.gz to /Users/gps/.rvm/archives
Extracting yaml to /Users/gps/.rvm/src/yaml-0.1.4
Configuring yaml in /Users/gps/.rvm/src/yaml-0.1.4.
Compiling yaml in /Users/gps/.rvm/src/yaml-0.1.4.
Installing yaml to /Users/gps/.rvm/usr
Installing Ruby from source to: /Users/gps/.rvm/rubies/ruby-1.9.3-p374, this may take a while depending on your cpu(s)...
ruby-1.9.3-p374 - #downloading ruby-1.9.3-p374, this may take a while depending on your connection...
ruby-1.9.3-p374 - #extracting ruby-1.9.3-p374 to /Users/gps/.rvm/src/ruby-1.9.3-p374
ruby-1.9.3-p374 - #extracted to /Users/gps/.rvm/src/ruby-1.9.3-p374
ruby-1.9.3-p374 - #configuring
ruby-1.9.3-p374 - #compiling
ruby-1.9.3-p374 - #installing
Extracting rubygems-1.8.24 ...
Error running '__rvm_package_extract /Users/gps/.rvm/archives/rubygems-1.8.24.tgz /Users/gps/.rvm/src', please read /Users/gps/.rvm/log/ruby-1.9.3-p374/rubygems.extract.log
Removing old Rubygems files...
Installing rubygems-1.8.24 for ruby-1.9.3-p374 ...
Error running 'env GEM_PATH=/Users/gps/.rvm/gems/ruby-1.9.3-p374:/Users/gps/.rvm/gems/ruby-1.9.3-p374@global:/Users/gps/.rvm/gems/ruby-1.9.3-p374:/Users/gps/.rvm/gems/ruby-1.9.3-p374@global GEM_HOME=/Users/gps/.rvm/gems/ruby-1.9.3-p374 /Users/gps/.rvm/rubies/ruby-1.9.3-p374/bin/ruby /Users/gps/.rvm/src/rubygems-1.8.24/setup.rb', please read /Users/gps/.rvm/log/ruby-1.9.3-p374/rubygems.install.log
Installation of rubygems did not complete successfully.
Saving wrappers to '/Users/gps/.rvm/bin'.
(gps ~)$ less .rvm/log/ruby-1.9.3-p374/rubygems.install.log
[2013-01-23 21:41:58] /Users/gps/.rvm/rubies/ruby-1.9.3-p374/bin/ruby
/Users/gps/.rvm/rubies/ruby-1.9.3-p374/bin/ruby: No such file or directory -- /Users/gps/.rvm/src/rubygems-1.8.24/setup.rb (LoadError)
Same missing setup.rb errors on CentOS 6.3 when installing ruby-1.9.3-p194.
@tylerjl did you do an rvm get head today? That's what I think broke mine.
Yep. Moreover this error shows up with just a vanilla
curl -L https://get.rvm.io | bash -s stable
on a pretty clean CentOS installation. I was getting strange errors so did an rvm implode followed by a reinstall of rvm and can't get gems working now.
could someone gist the $rvm_path/log/ruby-1.9.3-p374/rubygems.extract.log ?
Same problem here with ruby-1.9.3-p125-perf on a fresh ubuntu 10.04.
The /usr/local/rvm/log/ruby-1.9.3-p125-perf/rubygems.extract.log is empty
fix handling tgz packages, fix #1463
released RVM 1.18.1 with the fix
improved rubygems process, update #1463
after downloading the fix the installation of ruby 1.9.3 was successful however i still have these kind of problems after typing rvm use ruby-version@gemset --create --default:
rvm/scripts/selector: line 467: mkdir: command not found
.rvm/scripts/gemsets: line 176: mkdir: command not found
rvm/scripts/selector_gemsets: line 105: mkdir: command not found
-bash: ls: command not found
thanks in advance
@frankapimenta there was a bug in cleaning PATH and it was supposed to be fixed (we have tests to prevent it) - please open a new ticket and include echo $PATH before and after rvm use ...
rvm use ...