Skip to content

Instantly share code, notes, and snippets.

@leto
Last active August 29, 2015 14:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save leto/55aee8fd6c585546c3b2 to your computer and use it in GitHub Desktop.
Save leto/55aee8fd6c585546c3b2 to your computer and use it in GitHub Desktop.
Vagrant digital ocean plugin woes
$ vagrant install vagrant-digitalocean
Installing the 'vagrant-digitalocean' plugin. This can take a few minutes...
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:
An error occurred while installing nokogiri (1.6.4.1), and Bundler cannot continue.
Make sure that `gem install nokogiri -v '1.6.4.1'` succeeds before bundling.
$ sudo bash
# ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future gem install nokogiri -v '1.6.4.1'
Building native extensions. This could take a while...
Successfully installed nokogiri-1.6.4.1
Parsing documentation for nokogiri-1.6.4.1
unable to convert "\xCF" from ASCII-8BIT to UTF-8 for lib/nokogiri/nokogiri.bundle, skipping
Installing ri documentation for nokogiri-1.6.4.1
1 gem installed
Still the same issue persists. Then I tried:
$ ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future vagrant plugin install vagrant-digitalocean
Installing the 'vagrant-digitalocean' plugin. This can take a few minutes...
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:
An error occurred while installing nokogiri (1.6.4.1), and Bundler cannot continue.
Make sure that `gem install nokogiri -v '1.6.4.1'` succeeds before bundling.
Still same bug
The issues seem to be that ARCHFLAGS is not getting passed to the environment that vagrant is running "bundler install" from.
$ CPPFLAGS=/usr/local/opt/libiconv/include LDFLAGS=/usr/local/opt/libiconv/lib ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future /Applications/Vagrant/embedded/bin/gem install nokogiri -v '1.6.4.1'
Building native extensions. This could take a while...
ERROR: Error installing nokogiri:
ERROR: Failed to build gem native extension.
/Applications/Vagrant/embedded/bin/ruby 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... yes
Building nokogiri using packaged libraries.
checking for iconv using --with-opt-* flags... no
checking for iconv... no
-----
libiconv is missing. Please locate mkmf.log to investigate how it is failing.
-----
*** 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
--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=/Applications/Vagrant/embedded/bin/ruby
--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
Gem files will remain installed in /Applications/Vagrant/embedded/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.4.1 for inspection.
Results logged to /Applications/Vagrant/embedded/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.4.1/ext/nokogiri/gem_make.out
@leto
Copy link
Author

leto commented Dec 29, 2014

Vagrant 1.7 fixed all this poppycock

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment