System/Library/Frameworks/amework/Versions/2.3/usr/bin/ruby -r. This could take a while.ĮRROR: Failed to build gem native extension.Ĭurrent directory: /Library/Ruby/Gems/2.3.0/gems/http_parser.rb-0.6.0/ext/ruby_http_parser As it has been disclosed elsewhere and El Capitan is scheduled to ship next week, this is likely considered public knowledge.īuilding native extensions. The only change since then is (I think) Applications/Utilities, but as I am not running the GM build, I cannot verify this. Lastly, to provide a definitive answer regarding SIP and available directories, the following information is directly from Session 706. This probably will go away as 3.0 makes many things "opt-in", but it's still something to consider. Not as an outright requirement, but perhaps an "Information" block here. To facilitate that, might I suggest pointing to any of the various Ruby managers out there and people can choose which one suits their needs. While installing in the manner you suggest does solve the problem of putting Jekyll's Ruby in an isolated environment, I have had fewer gem conflicts when using a version that is slightly older than what Homebrew will give you. I'm almost certain I have a branch where I was working on this at some point, will take another In the past, I can recall discussions with the Core team regarding how the installation of Ruby should be handled.
0 kommentar(er)
