Updating to rails 2 2 2

Rated 3.99/5 based on 952 customer reviews

/usr/local/rvm/rubies/ruby-1.9.3-p392/bin/ruby *** failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. --curdir --ruby=/usr/local/rvm/rubies/ruby-1.9.3-p392/bin/ruby --with-atomic_reference-dir --without-atomic_reference-dir --with-atomic_reference-include --without-atomic_reference-include=$/include --with-atomic_reference-lib --without-atomic_reference-lib=$/lib /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/mkmf.rb:381:in `try_do': The compiler failed to generate an executable file.(Runtime Error) You have to install development tools first.

It might seem like a lot more work, but it’ll save you time in the long run. The newest point version of a Rails release has the best deprecation warnings.I searched Git Hub and people had already patched them.Made the upgrade much better then it could have been. I would have to agree with @dasil003 and say to check deprecations, and run your tests accordingly after updating.Here is the list of deprecations Of course the best way to quickly discover changes is to have a good test suite in place.If you don't have that, I suggest dropping 2.2 into vendor/rails and clicking around the site by hand. I had a bunch of plugins break with no official fixes.

Leave a Reply