Hello All,
I've been banging my head on this one as well. I even tried all the
tricks to install nokogiri from
http://nokogiri.org/tutorials/installing_nokogiri.html and
http://bullrico.com/2012/07/12/installing-nokogiri-after-updating-homebrew/
to no avail...
My ruby environment had no modifications prior to attempting this
upgrade.
Thanks,
Will
On 13 May 2014, at 14:16, Jon Buffington wrote:
Felipe,
Looks like this is bug in Vagrant 1.6.2:
$ vagrant --version
Vagrant 1.6.2
$ vagrant plugin list
vagrant-login (1.0.1, system)
vagrant-share (1.0.1, system)
vagrant-vmware-fusion (2.4.1)
$ vagrant plugin update vagrant-vmware-fusion
Updating plugins: vagrant-vmware-fusion. This may take a few
minutes...
Building nokogiri using packaged libraries.
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.2), and Bundler
cannot
continue.
Make sure that `gem install nokogiri -v '1.6.2'` succeeds before
bundling.
On Tuesday, May 13, 2014 2:41:35 AM UTC-4, Felipe Salum wrote:
Just ignore my previous email.
vagrant-windows is not compatible with Vagrant 1.6 (windows native
support). It was working in my other macbook because I had
vagrant-windows
installed before upgrading to vagrant 1.6.
On Monday, May 12, 2014 11:22:27 PM UTC-7, Felipe Salum wrote:
I'm trying to install a few vagrant plugins on my brand new Macbook
with
OSX 10.9.2 and Vagrant 1.6.2 but I keep getting the error below.
I have Xcode and command line tools installed. And I have nokogiri
1.6.2
gem installed already outside the vagrant embedded gem.
Not sure what is going on. I have it working in another macbook with
the
following warning message:
WARNING: Could not load IOV methods. Check your GSSAPI C library for
an update
WARNING: Could not load AEAD methods. Check your GSSAPI C library
for an update
WARNING: Nokogiri was built against LibXML version 2.8.0, but has
dynamically loaded 2.9.1
$ vagrant plugin install vagrant-windows
Installing the 'vagrant-windows' plugin. This can take a few
minutes...
Building nokogiri using packaged libraries.
Building libxml2-2.8.0 for nokogiri with the following patches
applied:
- 0001-Fix-parser-local-buffers-size-problems.patch
- 0002-Fix-entities-local-buffers-size-problems.patch
- 0003-Fix-an-error-in-previous-commit.patch
- 0004-Fix-potential-out-of-bound-access.patch
- 0005-Detect-excessive-entities-expansion-upon-replacement.patch
- 0006-Do-not-fetch-external-parsed-entities.patch
- 0007-Enforce-XML_PARSER_EOF-state-handling-through-the-pa.patch
- 0008-Improve-handling-of-xmlStopParser.patch
- 0009-Fix-a-couple-of-return-without-value.patch
- 0010-Keep-non-significant-blanks-node-in-HTML-parser.patch
- 0011-Do-not-fetch-external-parameter-entities.patch
************************************************************************
IMPORTANT! Nokogiri builds and uses a packaged version of libxml2.
If this is a concern for you and you want to use the system library
instead, abort this installation process and reinstall nokogiri as
follows:
gem install nokogiri -- --use-system-libraries
If you are using Bundler, tell it to use the option:
bundle config build.nokogiri --use-system-libraries
bundle install
However, note that nokogiri does not necessarily support all
versions
of libxml2.
For example, libxml2-2.9.0 and higher are currently known to be
broken
and thus unsupported by nokogiri, due to compatibility problems and
XPath optimization bugs.
************************************************************************
Building libxslt-1.1.28 for nokogiri with the following patches
applied:
- 0001-Adding-doc-update-related-to-1.1.28.patch
- 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
- 0003-Initialize-pseudo-random-number-generator-with-curre.patch
- 0004-EXSLT-function-str-replace-is-broken-as-is.patch
- 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
- 0007-Separate-function-for-predicate-matching-in-patterns.patch
- 0008-Fix-direct-pattern-matching.patch
- 0009-Fix-certain-patterns-with-predicates.patch
- 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
- 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
- 0014-Fix-for-bug-436589.patch
- 0015-Fix-mkdir-for-mingw.patch
************************************************************************
IMPORTANT! Nokogiri builds and uses a packaged version of libxslt.
If this is a concern for you and you want to use the system library
instead, abort this installation process and reinstall nokogiri as
follows:
gem install nokogiri -- --use-system-libraries
If you are using Bundler, tell it to use the option:
bundle config build.nokogiri --use-system-libraries
bundle install
************************************************************************
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.2), and Bundler
cannot
continue.
Make sure that `gem install nokogiri -v '1.6.2'` succeeds before
bundling.
--
You received this message because you are subscribed to the Google
Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
Will Froning
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
