Error installing gem - nokogiri 1.6.1

[masterninja01]

I can't seem to finish the installation of slogger. I ran into a problem installing the gem nokogiri 1.6.1. I had to go to another website for help. I followed the instructions to install the gems required. It ended up installing nokogiri-1.6.2.1 and mini_portile-0.6.0, which are different versions slogger tries to install initially. Is that a problem?

It said the installations were good. So I ran

./slogger --update-config

but got the normal error

Could not find nokogiri-1.6.1 in any of the sources
Run `bundle install` to install missing gems.

It ends up that the gem file for nokogiri is being kept for "inspection". What does that mean and how can I solve that problem.

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.1 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.1/ext/nokogiri/gem_make.out

And I know this might be better suited for stack-exchange or something. Just let me know if that's the case.

[larryhynes]

I'm guessing the nokogiri gem isn't being installed, hence the 'held for inspection' bit.

Have you tried sudo gem install nokogiri?

[wxn0000]

I had a similar problem with nokogiri.

Do you have libxml2 libxslt on your system? Do you use MacPorts?

I don't remember the exact command I used, but it was from the on-screen messages I saw during the failed attempt to install nokogiri gem. Could you paste the full log?

Xiaoning Wang

On Tue, Jun 3, 2014 at 10:19 AM, masterninja01 notifications@github.com wrote:

I can't seem to finish the installation of slogger. I ran into a problem installing the gem nokogiri 1.6.1. I had to go to another website http://nokogiri.org/tutorials/installing_nokogiri.html for help. I followed the instructions to install the gems required. It ended up installing nokogiri-1.6.2.1 and mini_portile-0.6.0, which are different versions slogger tries to install initially. Is that a problem?

It said the installations were good. So I ran

./slogger --update-config

but got the normal error

Could not find nokogiri-1.6.1 in any of the sources Run bundle install to install missing gems.

It ends up that the gem file for nokogiri is being kept for "inspection". What does that mean and how can I solve that problem.

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.1 for inspection. Results logged to /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.1/ext/nokogiri/gem_make.out

And I know this might be better suited for stack-exchange or something. Just let me know if that's the case.

— Reply to this email directly or view it on GitHub https://github.com/ttscoff/Slogger/issues/308.

[felciano]

I'm running into the same issue. Trying sudo gem install nokogiri gives the sam error re libxml2

[wxn0000]

take a look at this: http://stackoverflow.com/a/19807558 might work for you.

Xiaoning Wang (Travis)

On Sun, Jun 8, 2014 at 6:21 PM, Ramon Felciano notifications@github.com wrote:

I'm running into the same issue. Trying sudo gem install nokogiri gives the sam error re libxml2

— Reply to this email directly or view it on GitHub https://github.com/ttscoff/Slogger/issues/308#issuecomment-45450368.

[ghost]

I was able to get slogger to install after having the same issue. I'm on OS X 10.9.3. Here is what I did.

1. installed the Xcode command-line tools.
2. I renamed the file gemfile.lock. Not sure how smart that was :) but it specifies 1.6.1 of nokogiri and since I couldn't get that version to work I figured I didn't have much to lose ;)
3. I ran the commands here. That will install nokogiri 1.6.2.
4. Lastly I ran 'bundle install' for slogger.

I now have a working install and I never received any errors during the slogger install process.

Hope this helps someone!

[felciano]

I ended up with a similar workaround. The instructions on StackOverflow post got me nokogiri 1.2.6.1 installed. I updated the Gemfile.lock file to expect that version, after which bundle install worked.

[jannae]

Renaming gemfile.lock worked for me as well. Will keep an eye out for the official fix to this!

[durul]

I fixed this problem with this command.
export NOKOGIRI_USE_SYSTEM_LIBRARIES=true