Gem ext builderror error failed to build gem native extension

I run «bundle install».

➜ dailsoncampos git:(Production) ✗ bundle install
Fetching gem metadata from https://rubygems.org/………..
Fetching version metadata from https://rubygems.org/…
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies…
Using rake 11.1.2
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.8.4
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile2 2.0.0
Using rack 1.6.4
Using mime-types 2.99
Using arel 6.0.3
Using debug_inspector 0.0.2
Using bundler 1.11.2
Using coffee-script-source 1.10.0
Using execjs 2.6.0
Using thor 0.19.1
Using columnize 0.9.0
Using concurrent-ruby 1.0.1
Using debugger-linecache 1.2.0
Using debugger-ruby_core_source 1.3.8
Using multi_json 1.11.2
Using sass 3.4.22
Using tilt 2.0.2
Using spring 1.6.4
Using sqlite3 1.3.11
Using rdoc 4.2.2
Using tzinfo 1.2.2
Using nokogiri 1.6.7.2
Using rack-test 0.6.3
Using mail 2.6.3
Using binding_of_caller 0.7.2
Using coffee-script 2.4.1
Using uglifier 2.7.2
Using sprockets 3.5.2
Installing debugger 1.6.8 with native extensions

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

/home/campos/.rvm/rubies/ruby-2.1.8/bin/ruby -r ./siteconf20160423-10896-9be59d.rb extconf.rb

*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.

Provided configuration options:
—with-opt-dir
—without-opt-dir
—with-opt-include
—without-opt-include=${opt-dir}/include
—with-opt-lib
—without-opt-lib=${opt-dir}/lib
—with-make-prog
—without-make-prog
—srcdir=.
—curdir
—ruby=/home/campos/.rvm/rubies/ruby-2.1.8/bin/ruby
/home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:1401:in initialize': No such file or directory @ rb_sysopen - ./218/ruby_debug.h (Errno::ENOENT) from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:1401:inopen’
from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:1401:in copy_file' from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:483:incopy_file’
from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:400:in block in cp' from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:1579:inblock in fu_each_src_dest’
from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:1593:in fu_each_src_dest0' from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:1577:infu_each_src_dest’
from /home/campos/.rvm/rubies/ruby-2.1.8/lib/ruby/2.1.0/fileutils.rb:399:in cp' from extconf.rb:83:inblock in

‘
from extconf.rb:82:in each' from extconf.rb:82:in‘

extconf failed, exit code 1

Gem files will remain installed in /home/campos/.rvm/gems/ruby-2.1.8/gems/debugger-1.6.8 for inspection.
Results logged to /home/campos/.rvm/gems/ruby-2.1.8/extensions/x86_64-linux/2.1.0/debugger-1.6.8/gem_make.out
Using sdoc 0.4.1
Using activesupport 4.2.5.1
Using loofah 2.0.3
An error occurred while installing debugger (1.6.8), and Bundler cannot
continue.
Make sure that gem install debugger -v '1.6.8' succeeds before bundling.

Gem::Ext::BuildError: ERROR: Failed to build gem native extension. #3372

The text was updated successfully, but these errors were encountered:

• i do not believe this is an issue with bundler

this looks like a permissions error. Bundler expects that you have permission to write to the directory the error:
Permission denied @ dir_s_mkdir — ./.gem.20150131-61502-djrp3
as well as an error that came from mkdir both suggest incorrect permissions. If you are on OSX user this is probably due to the inappropriate use of sudo. OSX by convention doesn’t use sudo for much of any CLI installation unless you are using Macports

if you are using brew try brew doctor for help. or uninstall and reinstall rbenv (including it’s dependencies from

/.rbenv ) the try reinstalling this.

also rbenv doesn’t install bundler by default it is plausible that you are using system bundler to try and install nokogiri even though you are using rbenv’s ruby.

if you run which bundler and the return value is not rbenv something something try this:

gem install bundler && rbenv rehash

I agree, this looks like filesystem permissions are set up incorrectly. Check permissions on your project directory and on /Users/ratciti/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/nokogiri-1.6.6.2 (I believe it changes to the gem directory before building) to make sure you can write files as the user that you’re running Bundler with.

What resolved my issue was to install bundler without sudo. «gem install bundler».

Installing bundle «gem install bundler» also solved my similar issue

I was using rbenv in Fedora and got the same message. I couldn’t understand why.
At the end, it was a lack of underneath packages, it was solved installing them:
sudo dnf install ruby-devel cmake mariadb-devel rubygems-devel
bundler update
bundler install

it works for fedora 22 too.

solved the problem

Thanks for the info! I ran into this and this resolved the problem quickly.

sudo apt-get install ruby2.2-dev

This solution works perfectly for me. thanks to @Abdull
sudo apt-get install ruby2.2-dev
and after I ran
bundle install

I used sudo apt-get install ruby2.2-dev
But I’m getting the following error:
Reading package lists. Done
Building dependency tree
Reading state information. Done
E: Unable to locate package ruby2.2-dev
E: Couldn’t find any package by regex ‘ruby2.2-dev’

My problem is this «Make sure that gem install debugger -v ‘1.6.8’ succeeds before bundling». I’ve tried install it, but the problem continues.

Should probably run gem bundler install? If that is what you intend to use.
Ie «bundle exec» etc.

I also personally use rvm for my ruby versions. It seems more maintainable.
On Apr 22, 2016 10:50 PM, «Dailson Campos» notifications@github.com wrote:

My problem is this «Make sure that gem install debugger -v ‘1.6.8’
succeeds before bundling error». What can I do?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#3372 (comment)

I run «bundle install».

➜ dailsoncampos git:(Production) ✗ bundle install
Fetching gem metadata from https://rubygems.org/.
Fetching version metadata from https://rubygems.org/.
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies.
Using rake 11.1.2
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.8.4
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile2 2.0.0
Using rack 1.6.4
Using mime-types 2.99
Using arel 6.0.3
Using debug_inspector 0.0.2
Using bundler 1.11.2
Using coffee-script-source 1.10.0
Using execjs 2.6.0
Using thor 0.19.1
Using columnize 0.9.0
Using concurrent-ruby 1.0.1
Using debugger-linecache 1.2.0
Using debugger-ruby_core_source 1.3.8
Using multi_json 1.11.2
Using sass 3.4.22
Using tilt 2.0.2
Using spring 1.6.4
Using sqlite3 1.3.11
Using rdoc 4.2.2
Using tzinfo 1.2.2
Using nokogiri 1.6.7.2
Using rack-test 0.6.3
Using mail 2.6.3
Using binding_of_caller 0.7.2
Using coffee-script 2.4.1
Using uglifier 2.7.2
Using sprockets 3.5.2
Installing debugger 1.6.8 with native extensions

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

Источник

Installing Nokogiri¶

Welcome! We’ve worked hard to make Nokogiri easy and reliable to install. This page should hopefully get you on your way quickly.

The current version of this page focuses on the installation experience for Nokogiri v1.11 and later. If you’re trying to install an earlier version, please visit:

If this document doesn’t address your problem, please jump over to Getting Help.

If you’d like to contribute improvements to this document, please open a GitHub issue or pull-request on nokogiri.org/installing_nokogiri.md.

Installing Native Gems¶

Faster, more reliable installation¶

«Native gems» contain pre-compiled libraries for a specific machine architecture. On supported platforms, this removes the need for compiling the C extension and the packaged libraries, or to install system dependencies. This results in much faster installation and more reliable installation, which as you probably know have historically been challenging topics for Nokogiri users.

Supported Platforms¶

Nokogiri ships pre-compiled, «native» gems for the following platforms:

• Linux x86-linux and x86_64-linux (req: glibc >= 2.17 ) including musl/Alpine
• Linux aarch64-linux (req: glibc >= 2.29 ) including musl/Alpine
• MacOS x86_64-darwin and arm64-darwin
• Windows x86-mingw32 , x64-mingw32 , and x64-mingw-ucrt
• Java platforms running JRuby 9.3 or higher

To determine whether your system supports one of these gems, look at the output of bundle platform or ruby -e ‘puts Gem::Platform.local.to_s’ .

If you’re on a supported platform, either gem install or bundle install should install a native gem without any additional action on your part. This installation should only take a few seconds, and your output should look something like:

If you’re using Bundler >= 2.2 , check that your lockfile knows about your platform(s). For example, if you develop on macOS and deploy to Linux you will need to run these commands in your development environment:

See man bundle-lock for details.

Why would I not want to use a native gem?¶

I can imagine some folks might have trust issues; if this is you, please let us know in a comment at RFC: Increase the level of trust in released gem files · Issue #2013 · sparklemotion/nokogiri. What can we do to increase that trust? (I can imagine providing a chain of custody including public build logs with cryptographic hashes of artifacts, but I’d like to hear from real users.)

Anybody on a linux system with an unsupported version of glibc (see Supported Platforms) will need to install from the ruby platform gem.

If you’re on Termux, you will need to install from the ruby platform gem (see https://wiki.termux.com/wiki/Differences_from_Linux for background).

If you have other reasons for not wanting to use a precompiled native gem, let us know! (See Getting Help.)

How can I avoid using a precompiled native gem?¶

The Nokogiri maintainers strongly urge you to use a native gem if at all possible. We expect it will be a much better experience for you and allow us to focus our efforts on improving functionality rather than diagnosing installation issues.

If you’re on a platform that supports a native gem but you want to avoid using it in your project, do one of the following:

• With Bundler >= 2.3.18 , then update your Gemfile with gem «nokogiri», force_ruby_platform: true
• Else with Bundler >= 2.1 , then run bundle config set force_ruby_platform true ,
• Else with Bundler , then run bundle config force_ruby_platform true
• If you’re not using Bundler, then run gem install nokogiri —platform=ruby .

Installing the ruby platform gem¶

Again, we recommend that you upgrade to v1.11 or later and use a native gem whenever possible. If you’re here, it should be because you’re on an older version, or you’re on an unsupported platform.

Before you begin, make sure you have the full compiler toolchain for compiling Ruby C Extensions. See Appendix A: The Compiler Toolchain.

Installing Using The Packaged Libraries¶

Nokogiri packages its own updated and patched copies of libxml2 and libxslt source code. By default, installation of Nokogiri will compile and use these packaged libraries.

If you don’t see your operating system / distro in this section, then no additional setup is required beyond Appendix A: The Compiler Toolchain. Just run gem install nokogiri —platform=ruby .

Ubuntu or Debian-based Distros¶

You may substitute git for patch ( mini_portile2 can use either for applying patches).

Источник

Failed to build gem native extension #133

I met a snag as the following:

The version of Ruby installed is ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux-gnu]

Could anyone please tell me why and how to tackle it? Thanks very much.

The text was updated successfully, but these errors were encountered:

Did you also install the development headers? They don’t seem to be present:

Do you mean installing ruby-dev? But the error remains the same after that step.

apt-get install ruby-dev

You need the Ruby 2.1 dev headers. Maybe @envygeeks would know more on how to get them.

sudo apt-get install ruby2.1-dev for 2.1.

There is something wrong with your apt source, Brightbox Ruby does have ruby2.1-dev but you can’t even reach it, which leads me to believe you need to remove the source and readd it.

I get this error when running sudo gem update github-pages . Is this related?

Updating installed gems
Updating github-pages
Building native extensions. This could take a while.
ERROR: Error installing github-pages:
ERROR: Failed to build gem native extension.

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile

make «DESTDIR=»
make: *** No rule to make target /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin14/ruby/config.h’, needed by autolink.o’. Stop.

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/redcarpet-3.3.2 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/gems/redcarpet-3.3.2/ext/redcarpet/gem_make.out
Nothing to update

My Ruby version when running ruby -v is reported as:

ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]

@martinbean Related, yes, but on a different platform.

@parkr Strange. I’m not running El Capitan (still on Mavericks).

Check out the SDK version in that stack trace.

Closing as stale.

if using ruby version 2.2 or greater you need to have ruby2.2-dev

sudo apt-get install ruby2.2-dev

You might take a look

I am having a similar error on RHEL 7. I have also installed ruby-devel and am receving this error:

gem install tiny_tds —source http://rubygems.org
Building native extensions. This could take a while.
ERROR: Error installing tiny_tds:
ERROR: Failed to build gem native extension.

mkmf.rb can’t find header files for ruby at /opt/rh/rh-ruby22/root/usr/share/include/ruby.h

extconf failed, exit code 1

@midacts It looks like you’re using a custom version of Ruby installed to /opt/rh/rh-ruby22/root/usr . Installing ruby-devel won’t install the headers into this location, but into /usr/share/include/ruby.h instead. You will need to install the headers for the binary located at /opt/rh/rh-ruby22/root/usr/bin/ruby .

Hi @parkr Could you elaborate on how to do that? I’m a complete ruby noob, I’m just trying to get the knife-azure gem installed for chef, and am getting this message: current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.7.0.1/ext/nokogiri
/usr/bin/ruby2.3 -r ./siteconf20170220-10621-ejv836.rb extconf.rb
mkmf.rb can’t find header files for ruby at /usr/lib/ruby/include/ruby.h

I tried this command: sudo apt-get install ruby2.3-dev
Then tried to install gem again, got: E: Unable to locate package ruby2.3.0-dev

Any advice appreciated!

I’ve installed git for windows,JRuby,rjgit and gollum serval days ago,and they work well. But gollum doesn’t recognize the form of table.When i install github-markdown by the command of gem install github-markdown,the error comes.

I got error while installing gem install github-pages

windows 10 machine

I don’t know why I’m being pinged here, but switch to Linux on Windows, it’s better.

Hi there, sorry for respawning the thread but I preferred to do so as I think it applies to my issue.

I am trying to install Jekyll locally as per the official instructions. It fails when trying to build/install commonmarker:

Installing commonmarker 0.17.9 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory: /home/vincent/.gem/ruby/gems/commonmarker-0.17.9/ext/commonmarker
/usr/bin/ruby -r ./siteconf20180425-8716-wb76yr.rb extconf.rb
Ignoring ffi-1.9.18 because its extensions are not built. Try: gem pristine ffi —version 1.9.18
Ignoring json-1.8.6 because its extensions are not built. Try: gem pristine json —version 1.8.6
Ignoring nokogiri-1.7.1 because its extensions are not built. Try: gem pristine nokogiri —version 1.7.1
mkmf.rb can’t find header files for ruby at /usr/share/include/ruby.h
extconf failed, exit code 1
Gem files will remain installed in /home/vincent/.gem/ruby/gems/commonmarker-0.17.9 for inspection.
Results logged to /home/vincent/.gem/ruby/extensions/x86_64-linux/2.4.0/commonmarker-0.17.9/gem_make.out
An error occurred while installing commonmarker (0.17.9), and Bundler cannot continue.
Make sure that gem install commonmarker -v ‘0.17.9’ succeeds before bundling.
In Gemfile:
github-pages was resolved to 182, which depends on
jekyll-commonmark-ghpages was resolved to 0.1.5, which depends on
jekyll-commonmark was resolved to 1.2.0, which depends on
commonmarker

The issue is that ruby.h is present on my machine (this is Fedora 26), albeit in a different location: /usr/include/ruby.h

I have a workaround in that I just symlink /usr/share/include/ruby.h to that location but I am not sure what is the status of Jekyll support via Github on the various distros. Is that an expected error (I am a newbie for Ruby-related things)?

I had the same above issue but it turned out I did need to install the ruby headers

sudo apt-get install ruby-all-dev

Link to solutions for other distros: StackOverflow Answer

Mine also needed zlib, so:

sudo apt-get install zlib1g-dev

On a Mac, make sure that you have the commandline tools installed

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

26 Dec 2017

• Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
• uninitialized constant Gem::BundlerVersionFinder (NameError)
• can’t find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException)
  • sync Gemfile.lock to Bundler version
  • sync Bundler version to Gemfile.lock
• [__NSCFConstantString initialize] may have been in progress in another thread when fork() was called

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

the error occurred after installing a new Ruby version (2.5.0):

$ bundle
...
An error occurred while installing json (1.8.3), and Bundler cannot continue.
Make sure that `gem install json -v '1.8.3'` succeeds before bundling.

solution

try to update offending gem:

uninitialized constant Gem::BundlerVersionFinder (NameError)

$ berks
...
/Users/tap/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems/dependency.rb:283:in `matching_specs': uninitialized constant Gem::BundlerVersionFinder (NameError)

solution

error was gone after upgrading Ruby version from 2.5.0 to 2.5.1:

$ echo 2.5.1 > .ruby-version

if this doesn’t help, try to clean up old versions of installed gems (this will
remove currently installed versions as well):

gem cleanup removes bundled gems only (gems specified in Gemfile of current
project) though it might affect other projects if they are using the same gems
(run bundle for those projects as well in that case).

UPDATE

it has turned out the problem was caused by specific version of either
berkshelf or chef or both.

old versions (error is present):

gem 'berkshelf', '6.3.1'
gem 'chef', '13.5.3'

old versions (error is gone):

gem 'berkshelf', '7.0.2'
gem 'chef', '14.1.1'

can’t find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException)

$ bundle
Traceback (most recent call last):
	2: from /Users/tap/.rbenv/versions/2.5.0/bin/bundle:23:in `<main>'
	1: from /Users/tap/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems.rb:308:in `activate_bin_path'
/Users/tap/.rbenv/versions/2.5.0/lib/ruby/2.5.0/rubygems.rb:289:in `find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException)

solution

1. https://stackoverflow.com/a/54038218/3632318

find current Bundler version:

$ gem list --local bundler

*** LOCAL GEMS ***

bundler (2.0.2)

find Bundler version in Gemfile.lock:

# Gemfile.lock

BUNDLED WITH
  1.16.1

now there are 2 possible solutions:

sync Gemfile.lock to Bundler version

  # Gemfile.lock

  BUNDLED WITH
-   1.16.1
+   2.0.1

sync Bundler version to Gemfile.lock

1. https://bundler.io/blog/2019/01/04/an-update-on-the-bundler-2-release.html

$ gem install bundler -v 1.16.1

in many cases this solution is preferable since it’s easier and causes less
problems with CI and deployment.

[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called

$ rails console
[1] pry(main)> Profile.count
objc[29838]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[29838]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

solution

1. https://github.com/puma/puma/issues/2084

error has something to do with the latest version of psql (12.1) that must be
used by pg gem (psql is provided by libpq package in my case).

• edit libpq formula to install old version (11.7)

    # /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/libpq.rb
  
    class Libpq < Formula
      desc "Postgres C API library"
      homepage "https://www.postgresql.org/docs/12/libpq.html"
  -   url "https://ftp.postgresql.org/pub/source/v12.1/postgresql-12.1.tar.bz2"
  -   sha256 "a09bf3abbaf6763980d0f8acbb943b7629a8b20073de18d867aecdb7988483ed"
  +   url "https://ftp.postgresql.org/pub/source/v11.7/postgresql-11.7.tar.bz2"
  +   sha256 "324ae93a8846fbb6a25d562d271bc441ffa8794654c5b2839384834de220a313"
      revision 1
  

• reinstall libpq package from source

  $ brew reinstall libpq --build-from-source
  $ psql --version
  psql (PostgreSQL) 11.7
  

  if you try to install libpq bottle (without --build-from-source option),
  brew will fallback to building from source because old versions of libpq
  bottle are not available.

• reinstall pg gem to build native extensions against old version of libpq

  NOTE: it doesn’t work if you remove gem 'pg' from Gemfile manually and run
  bundle afterwards.

• rollback changes in libpq formula

  $ cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core
  $ git checkout Formula/libpq.rb
  $ cd -
  

• reinstall libpq package

  $ brew reinstall libpq
  $ psql --version
  psql (PostgreSQL) 12.1
  

Проблемы при генерации bundle install:

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory: /usr/local/rvm/gems/ruby-2.3.0/gems/json-1.8.1/ext/json/ext/generator
/usr/local/rvm/rubies/ruby-2.3.0/bin/ruby -r ./siteconf20160721-8878-1yafz8p.rb extconf.rb
creating Makefile

current directory: /usr/local/rvm/gems/ruby-2.3.0/gems/json-1.8.1/ext/json/ext/generator
make «DESTDIR=» clean

current directory: /usr/local/rvm/gems/ruby-2.3.0/gems/json-1.8.1/ext/json/ext/generator
make «DESTDIR=»
compiling generator.c
In file included from generator.c:1:0:
../fbuffer/fbuffer.h: In function ‘fbuffer_to_s’:
../fbuffer/fbuffer.h:175:47: error: macro «rb_str_new» requires 2 arguments, but only 1 given
VALUE result = rb_str_new(FBUFFER_PAIR(fb));
^
../fbuffer/fbuffer.h:175:20: warning: initialization makes integer from pointer without a cast [enabled by default]
VALUE result = rb_str_new(FBUFFER_PAIR(fb));
^
make: *** [generator.o] Error 1

make failed, exit code 2

Gem files will remain installed in /usr/local/rvm/gems/ruby-2.3.0/gems/json-1.8.1 for inspection.
Results logged to /usr/local/rvm/gems/ruby-2.3.0/extensions/x86_64-linux/2.3.0/json-1.8.1/gem_make.out
Using minitest 5.4.1
Using thread_safe 0.3.4
Using builder 3.2.2
Using erubis 2.7.0
Using rack 1.5.2
Using mime-types 1.25.1
Using polyglot 0.3.5
Using sass 3.2.19
Using thor 0.19.1
Using coffee-script-source 1.8.0
Using execjs 2.2.1
Using arel 5.0.1.20140414130214
Using bundler 1.12.5
Using hike 1.2.3
Using multi_json 1.10.1
Using tilt 1.4.1
Using addressable 2.3.6
Using bcrypt 3.1.7
Using coderay 1.1.0
Using debug_inspector 0.0.2
Using colorize 0.7.3
Using net-ssh 2.9.1
Using chunky_png 1.3.1
Using fssm 0.2.10
Using orm_adapter 0.5.0
Using libv8 3.16.14.3
Using modernizr-rails 2.7.1
Using normalize-rails 3.0.1
Using pg 0.17.1
Using ref 1.0.5
Using spring 1.1.3
An error occurred while installing json (1.8.1), and Bundler cannot continue.
Make sure that `gem install json -v ‘1.8.1’` succeeds before bundling.
~/workspace (master) $ gem list

*** LOCAL GEMS ***

actionmailer (4.2.5)
actionpack (4.2.5)
actionview (4.2.5)
activejob (4.2.5)
activemodel (4.2.5)
activerecord (4.2.5)
activesupport (4.2.5)
addressable (2.3.6)
arel (6.0.3, 5.0.1.20140414130214)
bcrypt (3.1.7)
bigdecimal (1.2.8)
binding_of_caller (0.7.2)
builder (3.2.2)
bundler (1.12.5)
bundler-unload (1.0.2)
byebug (9.0.5)
chunky_png (1.3.1)
coderay (1.1.0)
coffee-rails (4.1.1)
coffee-script (2.4.1)
coffee-script-source (1.10.0, 1.8.0)
colorize (0.7.3)
concurrent-ruby (1.0.2)
debug_inspector (0.0.2)
did_you_mean (1.0.0)
erubis (2.7.0)
execjs (2.7.0, 2.2.1)
executable-hooks (1.3.2)
fssm (0.2.10)
gem-wrappers (1.2.7)
globalid (0.3.6)
hike (1.2.3)
i18n (0.7.0, 0.6.11)
io-console (0.4.5)
jbuilder (2.5.0)
jquery-rails (4.1.1)
json (2.0.1, 1.8.3, 1.8.2)
libv8 (3.16.14.3 x86_64-linux)
loofah (2.0.3)
mail (2.6.4)
mime-types (3.1, 1.25.1)
mime-types-data (3.2016.0521)
mini_portile2 (2.1.0)
minitest (5.9.0, 5.8.3, 5.4.1)
modernizr-rails (2.7.1)
multi_json (1.12.1, 1.10.1)
net-ssh (2.9.1)
net-telnet (0.1.1)
nokogiri (1.6.8)
normalize-rails (3.0.1)
orm_adapter (0.5.0)
pg (0.17.1)
pkg-config (1.1.7)
polyglot (0.3.5)
power_assert (0.2.6)
psych (2.0.17)
rack (1.6.4, 1.5.2)
rack-test (0.6.3)
rails (4.2.5)
rails-deprecated_sanitizer (1.0.3)
rails-dom-testing (1.0.7)
rails-html-sanitizer (1.0.3)
railties (4.2.5)
rake (11.2.2, 10.4.2, 10.3.2)
rdoc (4.2.2, 4.2.1)
ref (1.0.5)
rubygems-bundler (1.4.4)
rvm (1.11.3.9)
sass (3.4.22, 3.2.19)
sass-rails (5.0.5)
sdoc (0.4.1)
spring (1.7.1, 1.1.3)
sprockets (3.6.2)
sprockets-rails (3.1.1)
sqlite3 (1.3.11)
test-unit (3.1.5)
thor (0.19.1)
thread_safe (0.3.5, 0.3.4)
tilt (2.0.5, 1.4.1)
turbolinks (5.0.0)
turbolinks-source (5.0.0)
tzinfo (1.2.2)
uglifier (3.0.0)
web-console (2.3)
~/workspace (master) $
Версии:
ruby 2.3.0
rails 4.2.5
Ни в какую,испробовал все.Есть ли лечение от зависимостей по данному вопросу?Спасибо.