Skip to content
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.

Install Jekyll Error #73

Closed
ghost opened this issue Jun 15, 2014 · 7 comments
Closed

Install Jekyll Error #73

ghost opened this issue Jun 15, 2014 · 7 comments

Comments

@ghost
Copy link

ghost commented Jun 15, 2014

I am installing jekyll using 'sudo gem install jekyll' on Yosemite 10.10 DP1. I get the following error.

ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
make: *** No rule to make target `/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin14/ruby/config.h', needed by `autolink.o'.  Stop.

make failed, exit code 2

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/redcarpet-3.1.2 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/extensions/universal-darwin-14/2.0.0/redcarpet-3.1.2/gem_make.out
@parkr
Copy link
Member

parkr commented Jun 15, 2014

You don't have the ruby headers:

ruby/config.h', needed by `autolink.o'

If you have homebrew installed, run brew install ruby and try again! @mattr- / @robin850 might have more knowledge of this particular area.

@robin850
Copy link

To be honest, I don't own a Mac so I don't know how you could install Ruby headers but this seems to be the answer. You may also encounter vmg/redcarpet#357. I hope it helps!

@ghost ghost closed this as completed Jun 15, 2014
@jaybe-jekyll
Copy link
Member

I feel compelled to point out and remind that executing sudo gem install anything on a *nix-based-derived machine is asking for and creating trouble, and is a poor approach to managing gems.

This link is python-based but described the general, consistent scenario, concerns, and pitfalls:

https://workaround.org/easy-install-debian

One would be better off, safer, and the system (especially the tinker-hostile OSX) positively intact by leveraging something such as homebrew, rbenv, rvm, chruby, etc. and or using gem with its native switches such as --user-install, etc.

@ghost
Copy link
Author

ghost commented Jun 15, 2014

parkr's suggestiion is ultimately what fixed the problem. Fyi jaybe-jekyll I installed several gems without any issues, though in some cases I did seem to have to re-update. As for robin850, that method is deprecated on Xcode 5.1.1 as Command Line Tools are now built in. Thanks all for the recommendations. Actually, I was trying to figure out an issue I am having with Opera malfunctioning in Yosemite 10.10 DP1 and began compile dev.opera not realizing Opera is not open source! dev.opera is their discussion forum for Opera development. That looks like it may be a kernel issue (unrelated to this discussion however). Thanks. Also, sorry for getting back so late, I ended up rashly deleting my ruby.framework and had to reinstall DP1. Yosemite 10.10 has been a challenge for software compatibility so far.

So, in conclusion in order to fix the error above just brew install ruby.

-Clay Spencer

@tannerjt
Copy link

Parkr's suggestion worked for me as well. Thanks!

@ghost
Copy link

ghost commented Jan 1, 2015

same issue here.
MAC OS X 10.9.5
ruby already installed by brew:

$ brew install ruby
Warning: ruby-2.2.0 already installed
$ sudo gem install jekyll
Password:
Building native extensions.  This could take a while...
ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile

make "DESTDIR="
make: *** No rule to make target `/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin13/ruby/config.h', needed by `yajl.o'.  Stop.


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

update: problem soved by adding ruby's path to the env.

@parkr
Copy link
Member

parkr commented Jan 2, 2015

Yep. It's asking for the ruby header files. In this case, ruby/config.h.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants