cannot install fulcrum - "bundle install" fails on nokogiri

[cp engr]

bundle install seems to be insisting on a specific version of nokogiri which is unavailable. What is the fix (or workaround) for this?

See my console output below

Thanks.


---------------------------------------

C:\Users\me\Documents\proj\agile\fulcrum>bundle install

DL is deprecated, please use Fiddle

Fetching gem metadata fromhttp://rubygems.org/.........

Fetching additional metadata fromhttp://rubygems.org/..

Resolving dependencies...

Using rake 10.1.1

Using i18n 0.6.9

Using minitest 4.7.5

Using multi_json 1.10.1

Using atomic 1.1.14

Using thread_safe 0.1.3

Using tzinfo 0.3.38

Using activesupport 4.0.2

Using builder 3.1.4

Using erubis 2.7.0

Using rack 1.5.2

Using rack-test 0.6.2

Using actionpack 4.0.2

Using mime-types 1.25.1

Using polyglot 0.3.3

Using treetop 1.4.15

Using mail 2.5.4

Using actionmailer 4.0.2

Using activemodel 4.0.2

Using activerecord-deprecated_finders 1.0.3

Using arel 4.0.1

Using activerecord 4.0.2

Using bcrypt-ruby 3.1.2

Using bundler 1.6.3

Using mini_portile 0.5.2

 

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension

.

 

    C:/Ruby200-x64/bin/ruby.exe extconf.rb

checking for libxml/parser.h... no

-----

libxml2 is missing.  please visithttp://nokogiri.org/tutorials/installing_nokog

iri.html for help with installing dependencies.

-----

*** 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

        --without-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=C:/Ruby200-x64/bin/ruby

        --with-zlib-dir

        --without-zlib-dir

        --with-zlib-include

        --without-zlib-include=${zlib-dir}/include

        --with-zlib-lib

        --without-zlib-lib=${zlib-dir}/lib

        --with-iconv-dir

        --without-iconv-dir

        --with-iconv-include

        --without-iconv-include=${iconv-dir}/include

        --with-iconv-lib

        --without-iconv-lib=${iconv-dir}/lib

        --with-xml2-dir

        --without-xml2-dir

        --with-xml2-include

        --without-xml2-include=${xml2-dir}/include

        --with-xml2-lib

        --without-xml2-lib=${xml2-dir}/lib

        --with-xslt-dir

        --without-xslt-dir

        --with-xslt-include

        --without-xslt-include=${xslt-dir}/include

        --with-xslt-lib

        --without-xslt-lib=${xslt-dir}/lib

        --with-libxslt-config

        --without-libxslt-config

        --with-pkg-config

        --without-pkg-config

        --with-libxml-2.0-config

        --without-libxml-2.0-config

        --with-pkg-config

        --without-pkg-config

        --with-libiconv-config

        --without-libiconv-config

        --with-pkg-config

        --without-pkg-config

 

 

Gem files will remain installed in C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nokog

iri-1.6.0 for inspection.

Results logged to C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.0/ext/nok

ogiri/gem_make.out

An error occurred while installing nokogiri (1.6.0), and Bundler cannot

continue.

Make sure that `gem install nokogiri -v '1.6.0'` succeeds before bundling.

 

C:\Users\me\Documents\proj\agile\fulcrum>bundle exec rake fulcrum:setup db:s

etup

DL is deprecated, please use Fiddle

Could not find nokogiri-1.6.0 in any of the sources

Run `bundle install` to install missing gems.

 

C:\Users\...\Documents\proj\agile\fulcrum>gem install nokogiri

Fetching: mini_portile-0.6.0.gem (100%)

Successfully installed mini_portile-0.6.0

Fetching: nokogiri-1.6.2.1-x64-mingw32.gem (100%)

Nokogiri is built with the packaged libraries: libxml2-2.8.0, libxslt-1.1.28, zl

ib-1.2.8, libiconv-1.14.

Successfully installed nokogiri-1.6.2.1-x64-mingw32

Parsing documentation for mini_portile-0.6.0

Installing ri documentation for mini_portile-0.6.0

Parsing documentation for nokogiri-1.6.2.1-x64-mingw32

unable to convert "\x90" from ASCII-8BIT to UTF-8 for lib/nokogiri/2.0/nokogiri.

so, skipping

unable to convert "\x90" from ASCII-8BIT to UTF-8 for lib/nokogiri/2.1/nokogiri.

so, skipping

Installing ri documentation for nokogiri-1.6.2.1-x64-mingw32

2 gems installed

 

C:\Users\me\Documents\proj\agile\fulcrum>bundle install

DL is deprecated, please use Fiddle

Fetching gem metadata fromhttp://rubygems.org/.........

Fetching additional metadata fromhttp://rubygems.org/..

Resolving dependencies...

Using rake 10.1.1

Using i18n 0.6.9

Using minitest 4.7.5

Using multi_json 1.10.1

Using atomic 1.1.14

Using thread_safe 0.1.3

Using tzinfo 0.3.38

Using activesupport 4.0.2

Using builder 3.1.4

Using erubis 2.7.0

Using rack 1.5.2

Using rack-test 0.6.2

Using actionpack 4.0.2

Using mime-types 1.25.1

Using polyglot 0.3.3

Using treetop 1.4.15

Using mail 2.5.4

Using actionmailer 4.0.2

Using activemodel 4.0.2

Using activerecord-deprecated_finders 1.0.3

Using arel 4.0.1

Using activerecord 4.0.2

Using bcrypt-ruby 3.1.2

Using bundler 1.6.3

Using mini_portile 0.5.2

 

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension

.

 

    C:/Ruby200-x64/bin/ruby.exe extconf.rb

checking for libxml/parser.h... no

-----

libxml2 is missing.  please visithttp://nokogiri.org/tutorials/installing_nokog

iri.html for help with installing dependencies.

-----

*** 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

        --without-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=C:/Ruby200-x64/bin/ruby

        --with-zlib-dir

        --without-zlib-dir

        --with-zlib-include

        --without-zlib-include=${zlib-dir}/include

        --with-zlib-lib

        --without-zlib-lib=${zlib-dir}/lib

        --with-iconv-dir

        --without-iconv-dir

        --with-iconv-include

        --without-iconv-include=${iconv-dir}/include

        --with-iconv-lib

        --without-iconv-lib=${iconv-dir}/lib

        --with-xml2-dir

        --without-xml2-dir

        --with-xml2-include

        --without-xml2-include=${xml2-dir}/include

        --with-xml2-lib

        --without-xml2-lib=${xml2-dir}/lib

        --with-xslt-dir

        --without-xslt-dir

        --with-xslt-include

        --without-xslt-include=${xslt-dir}/include

        --with-xslt-lib

        --without-xslt-lib=${xslt-dir}/lib

        --with-libxslt-config

        --without-libxslt-config

        --with-pkg-config

        --without-pkg-config

        --with-libxml-2.0-config

        --without-libxml-2.0-config

        --with-pkg-config

        --without-pkg-config

        --with-libiconv-config

        --without-libiconv-config

        --with-pkg-config

        --without-pkg-config

 

 

Gem files will remain installed in C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nokog

iri-1.6.0 for inspection.

Results logged to C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.0/ext/nok

ogiri/gem_make.out

An error occurred while installing nokogiri (1.6.0), and Bundler cannot

continue.

Make sure that `gem install nokogiri -v '1.6.0'` succeeds before bundling.

[cp engr]

Forgot to mention, this is on Windows 7 x64 with SP1.

[cp engr]

Here is my list of installed gems, if it helps.

----------------------------------------

C:\Users\me\Documents\proj\agile\fulcrum>gem list --local

*** LOCAL GEMS ***

actionmailer (4.1.4, 4.0.2)

actionpack (4.1.4, 4.0.2)

actionview (4.1.4)

activemodel (4.1.4, 4.0.2)

activerecord (4.1.4, 4.0.2)

activerecord-deprecated_finders (1.0.3)

activesupport (4.1.4, 4.0.2)

arel (5.0.1.20140414130214, 4.0.1)

atomic (1.1.14)

bcrypt-ruby (3.1.2 x64-mingw32)

bigdecimal (1.2.0)

builder (3.2.2, 3.1.4)

bundler (1.6.3)

erubis (2.7.0)

hike (1.2.3)

i18n (0.6.11, 0.6.9)

io-console (0.4.2)

json (1.7.7)

mail (2.5.4)

mime-types (1.25.1)

mini_portile (0.6.0, 0.5.2)

minitest (5.4.0, 4.7.5, 4.3.2)

multi_json (1.10.1)

nokogiri (1.6.2.1 x64-mingw32)

polyglot (0.3.5, 0.3.3)

psych (2.0.0)

rack (1.5.2)

rack-test (0.6.2)

rails (4.1.4)

railties (4.1.4)

rake (10.1.1, 0.9.6)

rdoc (4.0.0)

sprockets (2.12.1)

sprockets-rails (2.1.3)

test-unit (2.0.0.0)

thor (0.19.1)

thread_safe (0.3.4, 0.1.3)

tilt (1.4.1)

treetop (1.4.15)

tzinfo (1.2.1, 0.3.38)

[Malcolm Locke]

Hi cp engr,

That's correct, bundler has nokogiri locked at 1.6.0.

You could try the following:

bundle update nokogiri

which for me brings it up to 1.6.2.1. I'm not sure if that will fix
your problems. Google seems to show up several issues installing
nokogiri on 64 bit windows, but I'm not sure if the above version will
fix it.

Malc

> --
> You received this message because you are subscribed to the Google Groups "Fulcrum" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to fulcrum-user...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[cp engr]

I’m not sure I understand what you’re saying. You say that “bundle update nokogiri” will update it to a later version (1.6.2.1, which is what I have)…but that doesn’t help, since fulcrum is requiring 1.6.0. Why is this a requirement, anyway?

Nonetheless, I tried the command. The output is shown below.


I don’t know ruby. I’m lost.

---------------------------------------

C:\Users\me\Documents\proj\agile\fulcrum>bundle update nokogiri

DL is deprecated, please use Fiddle

Fetching gem metadata from http://rubygems.org/.........

Fetching additional metadata from http://rubygems.org/..

Using mini_portile 0.6.0 (was 0.5.2)

Using nokogiri 1.6.2.1 (was 1.6.0)

Installing xpath 2.0.0

Installing capybara 2.1.0

Installing json 1.8.1

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

C:/Ruby200-x64/bin/ruby.exe extconf.rb

Command 'qmake -spec win32-g++' not available

Gem files will remain installed in C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capyb

ara-webkit-1.0.0 for inspection.

Results logged to C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capybara-webkit-1.0.0/

./gem_make.out

An error occurred while installing capybara-webkit (1.0.0), and Bundler cannot continue.

Make sure that `gem install capybara-webkit -v '1.0.0'` succeeds before bundling.

[Malcolm Locke]

nokogiri is not a direct requirement of Fulcrum, it is a dependency of
one of Fulcrum's dependencies. Bundler comes up with a solution of
different versions of gems that are all compatible with each other.

By running `bundle update nokogiri` you are asking bundler to try and
find a newer version of nokogiri that still settles all of the
dependency requirements of the things that rely on nokogiri defined in
the application.

I'm afraid that Ruby support on Windows is not very good, and as a
consequence you're probably treading relatively unknown ground.

Are you able to google and find the minimum version of nokogiri that
will fix your compilation problem? If I know what the minimum version
you need is I might be able to come up with a fix.

Malc

[cp engr]

> nokogiri is not a direct requirement of Fulcrum, it is a dependency of
one of Fulcrum's dependencies.

Which package is requiring (at most version 1.6.0 of) nokogiri?

> Bundler comes up with a solution of
different versions of gems that are all compatible with each other.

If only they were all available...

> By running `bundle update nokogiri` you are asking bundler to try and
find a newer version of nokogiri that still settles all of the
dependency requirements of the things that rely on nokogiri defined in
the application.

As expected, this did not help, because I already have a newer version. The bundler configuration seems to be locking nokogiri to either a version ceiling (1.6.0 "at the latest"), or a specific version (1.6.0 exactly).

> I'm afraid that Ruby support on Windows is not very good, and as a
consequence you're probably treading relatively unknown ground.

Bummer. Thanks for the heads-up.

> Are you able to google and find the minimum version of nokogiri that
will fix your compilation problem? If I know what the minimum version
you need is I might be able to come up with a fix.

According to the error message, the *maximum* (or only) usable version is 1.6.0. If there were only a minimum requirement, I don't think I'd be having this problem.

[Malcolm Locke]

On Thu, Jul 17, 2014 at 03:15:03PM -0700, cp engr wrote:

> I’m not sure I understand what you’re saying. You say that “bundle
> update nokogiri” will update it to a later version (1.6.2.1, which is
> what I have)…but that doesn’t help, since fulcrum is requiring 1.6.0.
> Why is this a requirement, anyway?
>
> Nonetheless, I tried the command. The output is shown below.
>
>
> I don’t know ruby. I’m lost.
>
> ---------------------------------------
>
> C:\Users\me\Documents\proj\agile\fulcrum>bundle update nokogiri

> ---8<---

> Using nokogiri 1.6.2.1 (was 1.6.0)

So your original problem is fixed here ...

> ---8<---

> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
>
> C:/Ruby200-x64/bin/ruby.exe extconf.rb
>
> Command 'qmake -spec win32-g++' not available
>
> Gem files will remain installed in C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capyb
>
> ara-webkit-1.0.0 for inspection.
>
> Results logged to C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capybara-webkit-1.0.0/
>
> ./gem_make.out
>
> An error occurred while installing capybara-webkit (1.0.0), and Bundler cannot continue.
>
> Make sure that `gem install capybara-webkit -v '1.0.0'` succeeds before bundling.

... but now you have a new problem, capybara-webkit won't install.

The following seems to have some advice, I'm not sure how far it might
get you though:

https://groups.google.com/forum/#!topic/capybara-webkit/2tnnGLkrQkU

Sorry I can't be of more help :(

Malc

[Malcolm Locke]

On Thu, Jul 17, 2014 at 04:25:43PM -0700, cp engr wrote:
> > By running `bundle update nokogiri` you are asking bundler to try and
> find a newer version of nokogiri that still settles all of the
> dependency requirements of the things that rely on nokogiri defined in
> the application.

Can you do the following please (assuming you obtained your copy of
Fulcrum via `git clone`):

- Run `bundle update nokogiri`

- Send the output of `git diff Gemfile.lock`

Thanks,

Malc

[cp engr]

> > C:\Users\me\Documents\proj\agile\fulcrum>bundle update nokogiri

> > ---8<---

> > Using nokogiri 1.6.2.1 (was 1.6.0)

> So your original problem is fixed here ...

AFAIK, my “original problem” is that there is some gem (WHICH one?? I don't know how to tell) that will not accept any version of nokogiri later than 1.6.0—which is not available. AFAICT, I never even had 1.6.0, despite the implication of the output above. So I don’t see how this shows anything was fixed.

> - Run `bundle update nokogiri`

I did that before, as described in this post:
https://groups.google.com/d/msg/fulcrum-users/IaOf-pcPF0s/wD8B8-0qtigJ

Still, to be sure, I’ll do it again below.

> - Send the output of `git diff Gemfile.lock`

There is no output, i.e. no diff. No files have changed, and I have the latest master (1148c67) checked out, as shown (further) below.

Using xpath 2.0.0
Using capybara 2.1.0
Using json 1.8.1

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

C:/Ruby200-x64/bin/ruby.exe extconf.rb
Command 'qmake -spec win32-g++' not available

Gem files will remain installed in C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capybara-webkit-1.0.0 for inspection.

Results logged to C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capybara-webkit-1.0.0/./gem_make.out
An error occurred while installing capybara-webkit (1.0.0), and Bundler cannot continue.
Make sure that `gem install capybara-webkit -v '1.0.0'` succeeds before bundling.

------------------------------------------------------------------------

me@Win7PC /cygdrive/c/Users/me/Documents/proj/agile/fulcrum
$ git diff Gemfile.lock

me@Win7PC /cygdrive/c/Users/me/Documents/proj/agile/fulcrum
$ git diff

me@Win7PC /cygdrive/c/Users/me/Documents/proj/agile/fulcrum
$ git fetch

me@Win7PC /cygdrive/c/Users/me/Documents/proj/agile/fulcrum
$ git status
# On branch master
nothing to commit (working directory clean)

me@Win7PC /cygdrive/c/Users/me/Documents/proj/agile/fulcrum
$ git log --all --graph --decorate --pretty=oneline --abbrev-commit
* 1148c67 (HEAD, origin/master, origin/HEAD, master) Update selenium-webdriver t
* f71db17 Merge pull request #212 from kaleworsley/remove_i18n_js
|\
| * 12d25f9 Remove i18n-js gem.
* | e0f2e2b Update jasmine specs.
* | a440494 Fix story drag and drop reordering.
|/
* ac99c51 Silence deprecation for enforce_available_locales
* 265006b Upgrade rails to 4.0.2.
* 5590b0e Make story type case-insensitive on import.
* e10a774 Make state non-case-sensitive on import.
* 54d6d1e (origin/dstockdale-rails4-heroku) Move rails_12factor into production
...

[cp engr]

Any news on this? Are you still looking into this, or planning to?

If nothing else, I'd appreciate it if you could let me know how I can figure out which package is requiring the specific version of nokogiri. (Remember, I'm a Ruby neophyte.)

I hope I can try out your software. I enjoyed Pivotal Tracker, and now am in need of a task tracking solution that is not publicly hosted.

Thanks.

[Malcolm Locke]

On Fri, Jul 18, 2014 at 06:56:03AM -0700, cp engr wrote:
> > > C:\Users\me\Documents\proj\agile\fulcrum>bundle update nokogiri
> > > ---8<---
> > > Using nokogiri 1.6.2.1 (was 1.6.0)
>
> > So your original problem is fixed here ...
>
> AFAIK, my “original problem” is that there is some gem (WHICH one?? I
> don't know how to tell) that will not accept any version of nokogiri
> later than 1.6.0—which is not available. AFAICT, I never even had
> 1.6.0, despite the implication of the output above. So I don’t see how
> this shows anything was fixed.

Your original problem is the version of nokogiri that Fulcrum is
currently locked to (1.6.0) will not compile on your Win 64 system.

If you look at the output of `bundle update nokogiri` you will see it
gets past this step, but fails on another gem.

> > - Send the output of `git diff Gemfile.lock`
>
> There is no output, i.e. no diff. No files have changed, and I have
> the latest master (1148c67) checked out, as shown (further) below.

Yes, apologies, the Gemfile.lock hasn't been modified because the bundle
command still failed.

> C:\Users\me\Documents\proj\agile\fulcrum>bundle update nokogiri
> --- 8< ---

> Using capybara 2.1.0
> Using json 1.8.1
>
> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
>
> C:/Ruby200-x64/bin/ruby.exe extconf.rb
> Command 'qmake -spec win32-g++' not available
>
>
> Gem files will remain installed in C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capybara-webkit-1.0.0 for inspection.
> Results logged to C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/capybara-webkit-1.0.0/./gem_make.out
> An error occurred while installing capybara-webkit (1.0.0), and Bundler cannot continue.
> Make sure that `gem install capybara-webkit -v '1.0.0'` succeeds before bundling.

The gem that is now failing to compile is capybara-webkit.

I posted a link previously with some discussion on compiling
capybara-webkit on Windows, I'm not sure how helpful it will be:
https://groups.google.com/forum/#!topic/capybara-webkit/2tnnGLkrQkU

Given the error is `Command 'qmake -spec win32-g++' not available` I
suspect that you don't have the libqt development libraries installed.

Once you have capybara-webkit compiling, don't be surprised if there are
other failures :(

Malc

[cpengr]

> Your original problem is the version of nokogiri that Fulcrum is currently locked to (1.6.0) will not compile on your Win 64 system.

This is a difference of perspective. To my view, the problem is the version locking itself, i.e. capybara-webkit(?) ought not to be requiring anything other than the latest version of nokogiri.

In any case, I just spent ~1.5 hours trying to follow the complicated installation instructions for capybara-webkit, getting all the dependencies and everything... Some outputs didn't match up... And I did not succeed.

That's all the time I have to spend on this. If you ever get this issue resolved, I'd appreciate it if you'd reply to this thread to let me know. I remain interested in trying your software, but don't want to follow the mailing list for something I can't use.

Thanks kindly for for your time and effort.

--
You received this message because you are subscribed to a topic in the Google Groups "Fulcrum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fulcrum-users/IaOf-pcPF0s/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fulcrum-user...@googlegroups.com.