-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Closed
Labels
Description
Should be worth noting, anyone else out there seeing this error:
bd$ vagrant plugin install vagrant-aws
Installing the 'vagrant-aws' plugin. This can take a few minutes...
Fetching: ipaddress-0.8.3.gem (100%)
Fetching: mini_portile2-2.1.0.gem (100%)
Fetching: nokogiri-1.7.2.gem (100%)
Building native extensions. This could take a while...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
ERROR: Failed to build gem native extension.
/opt/vagrant/embedded/bin/ruby -r ./siteconf20170516-95228-gli9qd.rb extconf.rb
checking if the C compiler accepts ... yes
checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using packaged libraries.
Using mini_portile version 2.1.0
checking for iconv.h... yes
checking for gzdopen() in -lz... yes
checking for iconv using --with-opt-* flags... no
checking for iconv... no
pkg-config could not be used to find libiconv
Please install either `pkg-config` or the pkg-config gem per
gem install pkg-config -v "~> 1.1.7"
checking for iconv using pkg-config libiconv... no
-----
libiconv is missing. Please locate mkmf.log to investigate how it is failing.
-----
*** extconf.rb failed ***
The solution is to run export NOKOGIRI_USE_SYSTEM_LIBRARIES=true and then try to install the plugin again.
My system is clean OSX 10.12.5, nuked ~/.vagrant.d/gems, xcode-tools installed, no homebrew links of libxml, libxlst or any of that stuff.
Looks like Nokogiri gem was recently stripped from Vagrant, I'm figuring it had some magic in it to ensure the build flags were set correctly.
Reactions are currently unavailable