Installing sass on OS X 10.11 (El Capitan)

[aronstrandberg]

My sass gem "disappeared" after installing the OS X 10.11 beta, and re-installing it doesn't seem to work.

Running without sudo, I get this:

Ignoring json-1.8.2 because its extensions are not built.  Try: gem pristine json --version 1.8.2
Ignoring json-1.8.3 because its extensions are not built.  Try: gem pristine json --version 1.8.3
ERROR:  While executing gem ... (Errno::EACCES)
    Permission denied - /Library/Ruby/Gems/2.0.0/gems/sass-3.4.15/.yardopts

With sudo:

Ignoring json-1.8.2 because its extensions are not built.  Try: gem pristine json --version 1.8.2
Ignoring json-1.8.3 because its extensions are not built.  Try: gem pristine json --version 1.8.3
ERROR:  While executing gem ... (Errno::EPERM)
    Operation not permitted - /usr/bin/sass

Thoughts?

[nex3]

This looks like an OS problem rather than a Sass problem. We don't do anything to change the default installation process.

[nex3]

It looks like this is popping up for at least several users of El Capitan. I haven't the slightest idea why it would be happening, though, and it still looks like an OS issue. If someone who's running into it wants to dig in and see if they can find the root cause so we can maybe find a workaround, that would be appreciated.

[aronstrandberg]

I had trouble installing Jekyll too, and according to issue 3807 there, it seems the issue is Apple not bundling the Ruby development headers. I seem to have (kind of) solved it by running rvm install ruby-2.2-head --disable-binary.

Now, Sass works, but only after running rvm list every time I want to use it.

[chriseppstein]

I had to do the rootless thing to make sass and compass work. sudo nvram boot-args="rootless=0"; sudo reboot

https://twitter.com/cochinet/status/620624513919684609

[unclenorton]

Upgrading the Ruby version to 2.2.2 as per this instruction did the trick for me. You will also need to add the local .rbenv binary path (/Users/username/.rbenv/versions/2.2.2/bin) to your bash profile for convenience.

[ousenko]

Using home-brew or custom $GEM_HOME can help resolving the issue.
I made an installation of ruby via brew:

brew install ruby

Now the gem stuff seem to happen relative to my /usr/local/bin*

[miklb]

In case anyone else runs across this, latest public beta (5) resolves the Ruby issues, at least for me after updating my gems.

[Alan-Billi]

I'm on El Capitan Beta 6 and still having the same trouble.
Made a fresh install of all Homebrew/Ruby/Rails and still have it :(

[endoplasmic]

This should get you up and running: sudo gem install -n /usr/local/bin GEM_NAME_HERE

[ghelton]

@endoplasmic that worked for me thanks! 👍

[jacobmiller]

@unclenorton 's link to Gorails ruby upgrade instructions worked for me

[stgeorgiev]

@endoplasmic, thanks it worked.

[miklb]

I'm a Ruby n00b, but from what I've read, and being a perpetual beta user in all things dev, slowing down and re-reading everything works.

I did a clean install of Homebrew, used rbenv and triple checked all of the paths in my shell (that last part was key).

Also, take said n00b at face value, but using sudo with Ruby on a Mac sounds like a disaster long term from what I've extensively researched.