-
-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX 10.10.2 installation problem (1.6.6.2) #1235
Comments
Hi, Thanks for reporting this issue. First, I'd like to make sure you've followed the instructions here:
Can you confirm? If you're still having issues, then please provide complete versions of all your log files. Thanks. |
Yes, have followed it gem_make.out:
and /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.6.2/ext/nokogiri/tmp/x86_64-apple-darwin14/ports/libxml2/2.9.2/compile.log:
|
Paging @zenspider -- I don't know what to make out of these architecture mismatches. Do you have any questions or advice for @oliver-whiteman around how his system is configured? This is mystifying. |
OK, I have managed to get past that bit now by:
but now it's complaining about libxml2 missing:
even though earlier in the logs it has:
|
Never fear! Some dumbass from Seattle is here! |
Well... I can't test against 10.10.2 as it isn't released yet. :( |
I've upgraded my rubygems to be the same version. Assuming we have the same version of clang (not reported, but mine is below), then this is probably/hopefully just a beta-release OS problem.
|
Um... which is to say, everything installs fine on 10.10.1 w/ the same versions of everything. |
Looks like it. I suppose that is equal parts annoying and good news |
Similar problem here ( OS X 10.10.1
|
gem_make.out
|
Well, I gave up on trying to install the vendored xml2 and decided to use the system version instead. |
^^^^this Works perfectly for me too. Thanks @thiagomarzagao |
Looks like 10.10.2 dropped today. @zenspider is going to try to reproduce with the final (the above was with the beta). |
I just confirmed that nokogiri installed fine with stock ruby on 10.10.2 (final) for me. If there are still problems for you, we need to compare notes and see what variables are different. |
I must have messed up something on my environment then (though I followed all the steps). Sorry about that. The system xml2 worked for me. |
Great, thanks for letting us know! Closing. |
I'm experiencing the exact same problem on OS X Using the system libraries also fixed it for me, but I'm reporting the Macports bit in case it allows you to fix the root cause of the problem. |
Thanks @rsanchezsaez. I'm using Macports and your analysis fixed the issue for me. I simply renamed /opt/local, installed the gem, then move /opt/local back. |
I know this is OSX question but I actually googled it when searching for Ubuntu solution ...so: after upgrading to Rails 4.2.4 (which includes Nokogiri
or
|
For others coming into this...I encountered the same on OSX Sierra and Ruby 2.4.0. I don't know where the libxml2 I already had installed came from, but brew warned me another version was already linked to opt. I choose to force homebrew's version and nokogiri installed thereafter as follows... >> brew install libxml2
Warning: libxml2 is a keg-only and another version is linked to opt.
Use `brew install --force` if you want to install this version
>> brew install --force libxml2
Warning: libxml2-2.9.4_2 already installed, it's just not linked.
>> brew link --force libxml2
Linking /usr/local/Cellar/libxml2/2.9.4_2... 17 symlinks created
>> gem install nokogiri -v '1.7.0.1' -- --use-system-libraries --with-xml2-include=/usr/include/libxml2 --with-xml2-lib=/usr/lib
Building native extensions with: '--use-system-libraries --with-xml2-include=/usr/include/libxml2 --with-xml2-lib=/usr/lib'
This could take a while...
Successfully installed nokogiri-1.7.0.1
1 gem installed |
I have tried everything I can think of and find to get this installed but no luck!
Command being run is:
gem install nokogiri
Error:
compile.log makes a lot of complaints about being built for an i386 system for some reasons:
Happy to add any more info
The text was updated successfully, but these errors were encountered: