Error installing nokogiri error failed to build gem native extension

I try to clone this repo and run bundle install. The bundle process failed and throw this error:

    ...
    Installing nokogiri 1.6.2.1 with native extensions
    Building nokogiri using packaged libraries.

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

        /Users/zulhilmizainudin/.rvm/rubies/ruby-2.2.0/bin/ruby -r ./siteconf20151130-43880-pntnc6.rb extconf.rb
    Building nokogiri using packaged libraries.
    -----
    libiconv is missing.  please visit http://nokogiri.org/tutorials/installing_nokogiri.html for help with installing dependencies.
    -----
    *** 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=/Users/zulhilmizainudin/.rvm/rubies/ruby-2.2.0/bin/$(RUBY_BASE_NAME)
        --help
        --clean
        --use-system-libraries
        --enable-static
        --disable-static
        --with-zlib-dir
        --without-zlib-dir
        --with-zlib-include
        --without-zlib-include=${zlib-dir}/include
        --with-zlib-lib
        --without-zlib-lib=${zlib-dir}/lib
        --enable-cross-build
        --disable-cross-build

    extconf failed, exit code 1

    Gem files will remain installed in /Users/zulhilmizainudin/.rvm/gems/ruby-2.2.0/gems/nokogiri-1.6.2.1 for inspection.
    Results logged to /Users/zulhilmizainudin/.rvm/gems/ruby-2.2.0/extensions/x86_64-darwin-14/2.2.0-static/nokogiri-1.6.2.1/gem_make.out
    An error occurred while installing nokogiri (1.6.2.1), and Bundler cannot continue.
    Make sure that `gem install nokogiri -v '1.6.2.1'` succeeds before bundling.

Then I try to run this:

gem install nokogiri -v '1.6.2.1'

And now I get this error:

Building native extensions.  This could take a while...
Building nokogiri using packaged libraries.
ERROR:  Error installing nokogiri:
    ERROR: Failed to build gem native extension.

    /Users/zulhilmizainudin/.rvm/rubies/ruby-2.2.0/bin/ruby -r ./siteconf20151130-43942-1axq4sj.rb extconf.rb
Building nokogiri using packaged libraries.
-----
libiconv is missing.  please visit http://nokogiri.org/tutorials/installing_nokogiri.html for help with installing dependencies.
-----
*** 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=/Users/zulhilmizainudin/.rvm/rubies/ruby-2.2.0/bin/$(RUBY_BASE_NAME)
    --help
    --clean
    --use-system-libraries
    --enable-static
    --disable-static
    --with-zlib-dir
    --without-zlib-dir
    --with-zlib-include
    --without-zlib-include=${zlib-dir}/include
    --with-zlib-lib
    --without-zlib-lib=${zlib-dir}/lib
    --enable-cross-build
    --disable-cross-build

extconf failed, exit code 1

Gem files will remain installed in /Users/zulhilmizainudin/.rvm/gems/ruby-2.2.0/gems/nokogiri-1.6.2.1 for inspection.
Results logged to /Users/zulhilmizainudin/.rvm/gems/ruby-2.2.0/extensions/x86_64-darwin-14/2.2.0-static/nokogiri-1.6.2.1/gem_make.out

I tried to follow this answer but I still get the same error above.

I also try to uninstall and install my brew again (based on this answer) and it’s still same.

Also, I try this solution but still get the error.

What should I do now to make sure this nokogiri gem installed successfully?

Note: I’m using OSX 10.11.1 El Capitan.

Hi, i’m using OSX 10.9.2 and Ruby 2.1.1 installed with rbenv.
When running $ sudo gem install nokogiri -v '1.6.1' I receive the following error:

Building native extensions.  This could take a while...
ERROR:  Error installing nokogiri:
    ERROR: Failed to build gem native extension.

    /usr/local/var/rbenv/versions/2.1.1/bin/ruby extconf.rb
Extracting libxml2-2.8.0.tar.gz into tmp/i686-apple-darwin11/ports/libxml2/2.8.0... OK
Running 'configure' for libxml2 2.8.0... ERROR, review 'tmp/i686-apple-darwin11/ports/libxml2/2.8.0/configure.log' to see what happened.
*** 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=/usr/local/var/rbenv/versions/2.1.1/bin/ruby
/usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/mini_portile-0.5.3/lib/mini_portile.rb:278:in `block in execute': Failed to complete configure task (RuntimeError)
    from /usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/mini_portile-0.5.3/lib/mini_portile.rb:270:in `chdir'
    from /usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/mini_portile-0.5.3/lib/mini_portile.rb:270:in `execute'
    from /usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/mini_portile-0.5.3/lib/mini_portile.rb:65:in `configure'
    from /usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/mini_portile-0.5.3/lib/mini_portile.rb:108:in `cook'
    from extconf.rb:101:in `block in <main>'
    from extconf.rb:119:in `call'
    from extconf.rb:119:in `block in <main>'
    from extconf.rb:109:in `tap'
    from extconf.rb:109:in `<main>'

extconf failed, exit code 1

Gem files will remain installed in /usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/nokogiri-1.6.1 for inspection.
Results logged to /usr/local/var/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/extensions/x86_64-darwin-13/2.1.0-static/nokogiri-1.6.1/gem_make.out

I am using Homebrew and tried the installation steps listed on the nokogiri site:
brew install libxml2 libxslt
brew link libxml2 libxslt
wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.13.1.tar.gz
tar xvfz libiconv-1.13.1.tar.gz
cd libiconv-1.13.1
./configure --prefix=/usr/local/Cellar/libiconv/1.13.1
make
sudo make install
Then I tried installing passing in the options as specified below:
sudo gem install nokogiri -- --with-xml2-include=/usr/local/Cellar/libxml2/2.8.0/include/libxml2 --with-xml2-lib=/usr/local/Cellar/libxml2/2.8.0/lib --with-xslt-dir=/usr/local/Cellar/libxslt/1.1.28 --with-iconv-include=/usr/local/Cellar/libiconv/1.13.1/include --with-iconv-lib=/usr/local/Cellar/libiconv/1.13.1/lib'

This shows the same error as per above.

A google search shows that this can be a common error https://www.google.co.uk/search?q=Running+%27configure%27+for+libxml2+2.8.0…+ERROR%2C+review&oq=Running+%27configure%27+for+libxml2+2.8.0…+ERROR%2C+review&aqs=chrome..69i57j69i59j0.238j0j4&sourceid=chrome&es_sm=91&ie=UTF-8#q=Running+’configure’+for+libxml2+2.8.0…+ERROR%2C+review&safe=off

Some solutions recommend installing command line tools although I have xcode 5.1.1 which comes with command line tools I believe.

I have also tried specifying that nokogiri should use the system libraries as one answer suggested:
$ NOKOGIRI_USE_SYSTEM_LIBRARIES=1 gem install nokogiri

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).

Источник

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).

Источник

Nokogiri gem refuses to install #397

Thank you for this awesome app.

My objective is to install Rails in Termux but when it reach to the point of installing Nokogiri this is what I get:

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

Thanks, this was a regression after the recent gcc-to-clang transition, but has now been fixed int he latest clang package (version 3.8.1-2 ) — update to it with apt update && apt upgrade and try again!

I just did the upgrade of the clang package with apt update && apt upgrade , then I ran the gem install nokogiri — —use-system-libraries but I still get the error:

Have you installed the required packages?

Could you also try with running gem cleanup first? If the problem remains, can you attach the contents of

Also, check that you have the updated clang package:

yeah! it works! thanks @fornwall.

Hi. Didnt want to open a new issue, but I am having the same problem with nokogiri 1.7.0.1.

Any ideas? The output of

@SpriteMidr Have you installed dependencies with:

, run gem cleanup to ensure a clean build and then try to install nokogiri with:

If so, do you get the

Thank you very much for the help! Why do we need to
— —use-system-libraries ?

If -use-system-libraries is not specified, nokogiri tries building bundled versions of the libraries, and this does not work due to the build process assuming that /bin/sh exists (which while generally a valid assumption, is not true on Android).

@SpriteMidr termux-chroot is available for this purpose. Install proot package to get it.
termux-chroot drops you into a proot evironment with standard mountpoints. Its really handy for development purposes.

JFYI: I could install it with:
gem install nokogiri — —use-system-libraries —with-xml2-config=/data/data/com.termux/files/usr/bin/xml2-config —with-xml2-include=/data/data/com.termux/files/usr/include/libxml2

gem install nokogiri — —use-system-libraries not working.

`$ gem install nokogiri — —use-system-libraries
Building native extensions with: ‘—use-system-libraries’
This could take a while.
ERROR: Error installing nokogiri:
ERROR: Failed to build gem native extension.

/data/data/com.termux/files/usr/bin/ruby -r ./siteconf20180801-19990-qeeuh.rb extconf.rb —use-system-libraries
checking if the C compiler accepts . no
Building nokogiri using system libraries.
pkg-config could not be used to find libxml-2.0
Please install either pkg-config or the pkg-config gem per

pkg-config could not be used to find libxslt
Please install either pkg-config or the pkg-config gem per

pkg-config could not be used to find libexslt
Please install either pkg-config or the pkg-config gem per

Источник

Notes: Nokogiri installation errors on macos

Quick answer:
bundle config build.nokogiri —use-system-libraries && bundle install

This was originally posted on my blog here.

Every other year or so I want (or need) to install dependencies for a Ruby application on my Macbook, directly on the host instead of a VM or container. Mostly it’s a Rails app.

And every time our most “loved” dependency bails on me: nokogiri . I think it always fails on a Mac. (At least once.)

Because I never go directly to the documentation of whatever refuses to work, I usually google my way to a solution. In my case this was then harder than it should have been, so I write this down here for me as a reminder.

The next time I google it, I hope to find my own blog post and will make the same expression at the end. Again.

How does it fail

Try to get and build the dependencies:

And after a while …

Now if you run what is suggested …

You can also check the logs for later reference, too.

This is a problem that it cannot work with the iconv library currently present for linking. This can either be due to what was shipped with nokogiri or you have installed a different version via homebrew.

Alternatively also another library can cause some troubles: libxml2

Then the output might look like …

How to fix it

Well, if one would pay attention to the output, sometimes the output already tells you what could be done.

For the libxml case:

So, the last commands are the things you should consider for a bundler based project.

You can check the config:

/.bundle/config for completion:

And that’s it. Fixed!

Nokogiri documentation

If I had consulted the nokogiri documentation at all, I also would have got the hint earlier:

Nokogiri will refuse to build against certain versions of libxml2, libxslt supplied with your operating system, and certain versions will cause mysterious problems. The compile scripts will warn you if you try to do this.

It focuses on libxml2, but the steps also help with the libiconv issue, too.

Источник