rvm install 1.9.2 fails when running autoconf?
I figured it out. The key is this line:
ruby-1.9.2-p0 - #extracted to /Users/lee/.rvm/src/ruby-1.9.2-p0 (already extracted)
Apparently if there is an error during your first attempt the directory for the 1.9.2 package is not removed. (In my case, the autoconf files were not properly downloaded.) Any subsequent attempts see the directory and does not attempt to download the package again.
You need to remove the ruby-1.9.2-p0 directory. I assume this could be a problem with any version.
Hope this helps someone else.
Error running 'autoconf' when installing Ruby 1.9.3 using RVM
looks like ruby version was not detected properly, make sure you use up to date RVM:
curl -L https://get.rvm.io | bash
rvm reload
also specifying full version might help:
rvm install ruby-1.9.3-p194
Why do I get an Error running 'autoreconf' error using RVM to install ruby-2.0.0-head?
managed to fix the issue. It was a perl version problem.
The autoconf log was saying something like "This perl not built to support threads".
I had an older version of perl:
$ perl --version
This is perl 5, version 12, subversion 3 (v5.12.3) built for darwin-multi-2level
I did 'sudo port upgrade perl5' and after it successfully updated everything went smoothly.
Thanks for the help everyone! :)
Trouble Installing Ruby 1.9.2 with RVM Mac OS X
I don't know if you're still on it, but i succeeded just by doing this ::
sudo rm /usr/local/lib/libz.*
:)
Probably some software has installed a wrong lib... Well wrong architecture
rvm install: ruby installation error
Uninstall and reinstall rvm
with
bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer)
For posterity, I'll add that the part of the error that says
Installing Ruby from source to: /usr/share/...
is what got me thinking about a broken installation of rvm which, as I said, is normally entirely contained in the ~/.rvm
directory.
RVM 1.9.2 install fails on Cloud9 IDE — bash syntax error
A solution is to modify your PATH variable like from:
$ echo $PATH
/home/ubuntu/.nvm/v0.10.30/bin:/usr/local/rvm/gems/ruby-2.1.1@rails4/bin:/usr/local/rvm/gems/ruby-2.1.1@global/bin:/usr/local/rvm/rubies/ruby-2.1.1/bin:/mnt/shared/bin:/home/ubuntu/workspace/node_modules/.bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/mnt/shared/sbin:/opt/gitl:/opt/go/bin:/mnt/shared/c9/app.nw/bin:/usr/local/rvm/bin
to
$ export PATH=/home/ubuntu/.nvm/v0.10.30/bin:/usr/local/rvm/gems/ruby-2.1.1@rails4/bin:/usr/local/rvm/gems/ruby-2.1.1@global/bin:/usr/local/rvm/rubies/ruby-2.1.1/bin:/home/ubuntu/workspace/node_modules/.bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/mnt/shared/sbin:/opt/gitl:/opt/go/bin:/mnt/shared/c9/app.nw/bin:/usr/local/rvm/bin:/mnt/shared/bin
Note the /mnt/shared/bin
dir is now at the last position of the PATH variable.
rvm install ruby-1.9.3-p286: Error running 'make -j 9' (OSX: Mountain Lion)
This took me forever to hunt down. Was trying different versions of make
, gcc
, etc.
It turns out the format of the rvm_make_flags
environment variable has changed from a string to an array and was not well communicated or documented. This may apply to all rvm_* env variables, not sure.
Check your ~/.rvmrc
and project/path/.rvmrc
.
# before
export rvm_make_flags="-j 9"
# after
export rvm_make_flags=(-j 9)
After making this change everything compiled cleanly.
Related Topics
Sending Http Post Request in Ruby by Net::Http
Superclass Mismatch, Struct, Reloading and Spork
Gemfile.Lock Always Has Changes Not Staged for Commit
Undefined Method 'Reset' for Rdoc::Toplevel:Class When Installing a New Ruby Gem
How Does Rake Db::Migrate Actually Work
Undefined Method 'Devise' When Including User Model Outside Rails
Ruby (With Rails) Convert a String of Time into Seconds
Ruby Gem Installation Error After Osx Yosemite and Xcode 6 Installation
Alter Rails Params Hash from Rack Middleware
Ruby on Rails Looks for CSS in Assets Instead of Public/Stylesheets
Invoking Knife in a Ruby Class
Download File from S3 to Rails 4 App
Ruby Yaml Parser by Passing Constructor
Capturing Logger Output Inside a Method
Raise Exception on Shell Command Failure
What's the Best Way to Start a Background Process, That Can Get Accessed Later On