Nokogiri packages its own updated and patched copies of libxml2 and libxslt source code. Installing Using The Packaged Libraries ¶
#RUBYINSTALLER 1.8.1 FULL#
If you're here, it should be because you're on an older version, or you're on an unsupported platform.īefore you begin, make sure you have the full compiler toolchain for compiling Ruby C Extensions.
#RUBYINSTALLER 1.8.1 INSTALL#
If you're not using Bundler, then run gem install nokogiri -platform=ruby.Īgain, we recommend that you upgrade to v1.11 or later and use a native gem whenever possible.Else with Bundler Else with Bundler >= 2.1, then run bundle config set force_ruby_platform true,.
#RUBYINSTALLER 1.8.1 UPDATE#
With Bundler >= 2.3.18, then update your Gemfile with gem "nokogiri", force_ruby_platform: true.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: 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. The Nokogiri maintainers strongly urge you to use a native gem if at all possible. 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? ¶ If you're on Termux, you will need to install from the ruby platform gem (see for background). 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.)Īnybody on a linux system with an unsupported version of glibc (see Supported Platforms) will need to install from the ruby platform 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 Why would I not want to use a native gem? ¶ This installation should only take a few seconds, and your output should look something like:īundle install # resolve dependencies for platform-specific gems 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. To determine whether your system supports one of these gems, look at the output of bundle platform or ruby -e 'puts Gem::_s'. Java platforms running JRuby 9.3 or higher.Linux aarch64-linux (req: glibc >= 2.29) including musl/Alpine.Linux x86-linux and x86_64-linux (req: glibc >= 2.17) including musl/Alpine.Nokogiri ships pre-compiled, "native" gems for the following platforms: This results in much faster installation and more reliable installation, which as you probably know have historically been challenging topics for Nokogiri users. On supported platforms, this removes the need for compiling the C extension and the packaged libraries, or to install system dependencies. "Native gems" contain pre-compiled libraries for a specific machine architecture. Installing Native Gems ¶ Faster, more reliable installation ¶ If you'd like to contribute improvements to this document, please open a GitHub issue or pull-request on /installing_nokogiri.md. If this document doesn't address your problem, please jump over to Getting Help. Nokogiri v1.10.x installation instructions.If you're trying to install an earlier version, please visit: The current version of this page focuses on the installation experience for Nokogiri v1.11 and later. This page should hopefully get you on your way quickly. Welcome! We've worked hard to make Nokogiri easy and reliable to install.
error: use of undeclared identifier 'LZMA_OK'
xcode-select errors with a 'network problem' Using vendor/cache to deploy to another architecture Installing Third-Party Distributions of NokogiriĬannot load such file - nokogiri/nokogiri (LoadError) Installing With Custom / Non-Standard Libraries Installing Using Standard System Libraries How can I avoid using a precompiled native gem? Why would I not want to use a native gem?
0 kommentar(er)
