New Rails Project: 'bundle install' can't install rails in gemfile - ruby-on-rails

Question

I have installed a new rails project like so:
$ rails new site
and it executes and reaches:
bundle install
but then I get this error, when it appears to try installing a dependency
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
checking for libkern/OSAtomic.h... yes
creating Makefile
make "DESTDIR=" clean
make "DESTDIR="
compiling atomic_reference.c
atomic_reference.c:57:59: warning: incompatible pointer types passing 'void **' to parameter of type 'volatile int64_t *' (aka 'volatile long long *') [-Wincompatible-pointer-types]
if (OSAtomicCompareAndSwap64(expect_value, new_value, &DATA_PTR(self))) {
^~~~~~~~~~~~~~~
/usr/include/libkern/OSAtomic.h:507:93: note: passing argument to parameter '__theValue' here
bool OSAtomicCompareAndSwap64( int64_t __oldValue, int64_t __newValue, volatile int64_t *__theValue );
^
1 warning generated.
linking shared-object atomic_reference.bundle
clang: error: unknown argument: '-multiply_definedsuppress' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make: *** [atomic_reference.bundle] Error 1
make failed, exit code 2
Gem files will remain installed in /Users/mikeguppy/.bundler/tmp/26234/gems/atomic-1.1.16 for inspection.
Results logged to /Users/mikeguppy/.bundler/tmp/26234/extensions/universal-darwin-13/2.0.0/atomic-1.1.16/gem_make.out
An error occurred while installing atomic (1.1.16), and Bundler cannot continue.
Make sure that `gem install atomic -v '1.1.16'` succeeds before bundling.
I have then tried installing atomic independently with:
gem install atomic
and again no luck.
I'm running Ruby 2.0 on Mac OS 10.9.2
Any help would be much appreciated!

Answer 1

this worked for me:
sudo ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future gem install rails

Answer 2

I had this same problem and what worked for me was installing RVM, installing Ruby 2.1.1 (an upgrade from the 2.0 that comes packaged in Mavericks)...
rvm get stable
rvm reinstall 2.1.1
(use whatever the latest version is, for me that's 2.1.1)
...and then run rvm use 2.1.1 to make sure that I had switched to using that version.
After that, my gem installs ran smoothly.

Answer 3

This appears to be an issue relating to the system Ruby that is packaged with Mavericks (2.0.0p247), see details about the bug here: https://bugs.ruby-lang.org/issues/9624
I got around this by installing rbenv (or RVM if you prefer) and then installing Ruby 2.1.1 so as not to tamper with the system Ruby version. You will still get a warning during the installation of the atomic gem but it won't fail at least.
rbenv here: https://github.com/sstephenson/rbenv

Answer 4

I had the same problem when installed rails.
My ruby version is 1.9.3 p448 and OS is OS X Mavericks (10.9.2).
Here's what I tried and it works.
$ gem install rails --version 4.0.4
[ref]
http://ruby.railstutorial.org/chapters/beginning#top

Answer 5

First uninstall any existing atomic gem
gem uninstall atomic
Then reinstall it using
gem install atomic -v '1.1.16'
After this try to create a new rails application
rails new projectname
I don't know which version of Rails you are currently using. Sometimes, re-installing Rails to a stable version seems to help. You may want to try that as well if the above steps didn't resolve the issue.

Answer 6

I had a similar problem recently and it was because Xcode updated automatically to 5.1. This version contains a bug/problem with gcc.
The clue is here:
-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning)
Sadly I had to downgrade Xcode - available here.

Answer 7

Ruby 2.1.5 on Maverick via rvm installed atomic 1.1.16 without issue.

Answer 8

This error can occur if you are bundling with the wrong version of ruby for the bundle. Check the Gemfile for the ruby version and then check the output of ruby -v. If there is a version mismatch, use rvm to make sure you are using the same version of ruby, then re-bundle.
I got this exact error and fixed it by changing the version of ruby I was using.

Answer 9

None of these worked for me. I came up with my own solution. The problem lies in json versions less than 2.0. When I tried to upgrade json, I got an error message about dependency issues with rails and sdoc. Here's what I ended up doing:
Open your Gemfile.
Comment out the lines for sdoc and rails.
Add this line:
gem 'json', '> 2'
Run bundle install.
Worked for me.