Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Bundle Install Crashing on JSON 1.6.6 #1809

Closed
jjstafford opened this Issue Apr 1, 2012 · 5 comments

Comments

Projects
None yet
6 participants

bundle install
Fetching gem metadata from https://rubygems.org/.......
Using rake (0.9.2.2)
Using i18n (0.6.0)
Installing multi_json (1.2.0)
Using activesupport (3.2.1)
Using builder (3.0.0)
Using activemodel (3.2.1)
Using erubis (2.7.0)
Using journey (1.0.3)
Using rack (1.4.1)
Using rack-cache (1.2)
Using rack-test (0.6.1)
Using hike (1.2.1)
Using tilt (1.3.3)
Using sprockets (2.1.2)
Using actionpack (3.2.1)
Installing mime-types (1.18)
Using polyglot (0.3.3)
Using treetop (1.4.10)
Installing mail (2.4.4)
Using actionmailer (3.2.1)
Using arel (3.0.2)
Using tzinfo (0.3.32)
Using activerecord (3.2.1)
Using activeresource (3.2.1)
Using bootstrap-sass (2.0.1)
Using coffee-script-source (1.2.0)
Using execjs (1.3.0)
Using coffee-script (2.2.0)
Using rack-ssl (1.3.2)
Installing json (1.6.6) with native extensions Unfortunately, a fatal error has occurred. Please report this error to the Bundler issue tracker at https://github.com/carlhuda/bundler/issues so that we can fix it. Thanks!
/Users/J/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:552:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)

    /Users/J/.rvm/rubies/ruby-1.9.3-p0/bin/ruby extconf.rb 

creating Makefile

make
sh: make: command not found

Gem files will remain installed in /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/json-1.6.6 for inspection.
Results logged to /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/json-1.6.6/ext/json/ext/generator/gem_make.out
from /Users/J/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:530:in block in build_extensions' from /Users/J/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:505:ineach'
from /Users/J/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:505:in build_extensions' from /Users/J/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:180:ininstall'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/source.rb:90:in block in install' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/rubygems_integration.rb:82:inpreserve_paths'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/source.rb:89:in install' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/installer.rb:73:inblock in install_gem_from_spec'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/rubygems_integration.rb:97:in with_build_args' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/installer.rb:72:ininstall_gem_from_spec'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/installer.rb:56:in block in run' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/installer.rb:55:inrun'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/installer.rb:12:in install' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/cli.rb:220:ininstall'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/vendor/thor/task.rb:22:in run' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/vendor/thor/invocation.rb:118:ininvoke_task'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/vendor/thor.rb:263:in dispatch' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/lib/bundler/vendor/thor/base.rb:386:instart'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/gems/bundler-1.1.0/bin/bundle:13:in <top (required)>' from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/bin/bundle:19:inload'
from /Users/J/.rvm/gems/ruby-1.9.3-p0@rails313/bin/bundle:19:in `

'

Environment: Mac OS X 10.7.3. New project.

Gemfile:

gem 'rails', '3.2.1'

gem 'mysql2'

group :production do
gem "pg"
end

group :assets do
gem 'sass-rails', '> 3.2.3'
gem 'coffee-rails', '
> 3.2.1'
gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails'

gem "nifty-generators", :group => :development

gem 'thin'

gem 'bootstrap-sass'

I am facing similar issue with ruby 1.9.2+ ON Mac OSX 1.7.2 Lion

Installing json (1.6.6) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

    /Users/nilesh/.rvm/rubies/ruby-1.9.2-p290/bin/ruby extconf.rb 

creating Makefile

make
.
.
.
An error occured while installing json (1.6.6), and Bundler cannot continue.
Make sure that gem install json -v '1.6.6' succeeds before bundling.

hzamani commented Apr 9, 2012

This is not a bundler issue, it seems that json 1.6.6 has a problem

flori commented May 8, 2012

@srawlins No, this problem is caused by make not being found, see above:

sh: make: command not found

flori/json#127 is caused by /usr/include/assert.h not being there, flori/json#128 by /bin/install not being there. Of course all these files should be there, somewhere in the path, or at these locations. You need a build system to install ordinary ruby extensions. If one installs a new build system which changes build executable paths one has to rebuild ruby with this new build system, otherwise it cannot find the required executables.

There's also the problem that older ruby versions cannot be compiled (without patches) on Apples's llvm-gcc that comes with xcode 4.3.x. In this case you can use one of the packages from here: https://github.com/kennethreitz/osx-gcc-installer

This is not a json problem, json just is the unlucky gem that needs to compile a c extension and wasn't compiled, and therefore stumbles over people's broken ruby/build systems and makes the problem apparent.

@rohit rohit closed this Nov 20, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment