bundle install with Nokogiri gem fails #278
Comments
|
This looks like it's an issue with nokogiri itself, not ChefDK, since it's just the compiler bombing on some C header files it doesn't like. With ChefDK does have libxml so this suggestion from the error output should work: You could also lock your Gemfile to the version of nokogiri included with ChefDK. |
|
Thanks @danielsdeleo. Locking to nokogiri 1.6.4.1 in the Gemfile resolves the issue. There must be something else to it though, as the Just read that nokogiri 1.6.4+ comes with it's own vendored libxml2 and libxslt: In the error output above it fails while trying to compile the nokogiri-vendored libxml2. Maybe some missing header files... |
|
Oh, it was
In short, |
|
FWIW, here's how we're building nokogiri w/ omnibus: https://github.com/opscode/omnibus-software/blob/e84914afce6feb98edcb718cf27fd9a2467e9187/config/software/nokogiri.rb#L68-L78 |
|
Here is alternate way or just add this env variable to Gemfile https://github.com/3ofcoins/opscode-omnibus-software/blob/master/config/software/chefdk.rb#L38-L43 |
|
Yes, "sudo apt-get install liblzma-dev zlib1g-dev" solves the issue. Bliss, --G |
|
Wow. This was intense, but thanks @kaustubh-d. Your ENV settings was by far the easiest fix :) |
|
@guangyu-shi thanks! That worked for me |
|
@guangyu-shi +1 |
Updated lock file to pull in new omnibus-software which includes AIX ope...
|
For RHEL7, |
|
@tknerr this solved it, I'm so new at this that I don't know why or what the problem was but |
|
Lets stop add metoos to this thread. Compiling nokogiri is hard. By far the easiest thing you can do is pin the exact version of nokogiri in your Gemfile to the version of nokogiri that we ship in the chef-dk that you are using. gem "nokogiri", "= 1.6.7.2"^^^ use whatever version The next best solution is to follow @kaustubh-d's recommendation which will cause the nokogiri that you build to link the same as the nokogiri that we ship: PKG_CONFIG_PATH=/opt/chefdk/embedded/lib/pkgconfig bundle installor: or just add this env variable to Gemfile
ENV['PKG_CONFIG_PATH'] = '/opt/chefdk/embedded/lib/pkgconfig'
gem 'nokogiri'If you don't feel like doing that, then you can attempt to link nokogiri against your system libraries. You'll need to install compilers and build tools, along with the header files for zlib, possibly lzma, and maybe libxml2 and libxslt, along with whatever else might become necessary in the future: for RHEL/CentOS something like: yum install gcc make zlib-devel liblzma-devel zlib-devel libxml2-devel libxslt-develor for Ubuntu/Debian some variant of: apt-get install build-essential liblzma-dev zlib1g-dev libxml2-dev libxslt-devPinning nokogiri (at the top) will generally be vastly easier to use and maintain than the other solutions. |
|
^ note that last idea is pretty bad. if you start building against system libraries you can wind up in a situation where the omnibus ruby binary links against omnibus-installed versions of those libraries but nokogiri pulls in system versions and that can create bad conflicts (see what happens with omnibus ruby linking against omnibus openssl and the gyrations that the postgresql cookbook has to go through in order to link postgres and the pg gem against the embedded version of openssl to avoid that kind of conflict). TL;DR: either use the version of nokogiri that ships with chefdk, or use PKG_CONFIG_PATH to link against the libraries that ship in chef-dk. |
Ohai!
Trying to use ChefDK 0.3.5 on Ubuntu 14.04 with a sample cookbook. It fails during
bundle installwhen trying to compile the Nokogiri native gem.This is what I did:
Looking at the compile.log, I see this:
I'm wondering why it even tries to compile nokogiri as it is shipped with chefdk already afaik.
Any ideas?
The text was updated successfully, but these errors were encountered: