-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Getting error after upgrading to MacOS High Sierra #2129
Comments
+1 did you come up with a fix? |
High Sierra uses ruby v2.3x as 2.0 seems to be deprecating. I found a workaround that involves installing ruby 2.0 via rvm. https://rvm.io/. Hopefully compass will compatibility in the future. You can use the follow terminal commands
Compass should work as is afterwards. Good luck |
+1 Sass and Compass all have the same problem. When Install again another problem comes like: |
reinstall compass fix it |
After upgrading to macOS High Sierra, get it fixed with following commands: |
I was able to fix it with a slightly modified answer from oklai/koala#679
At this point, install Compass (instead of SASS in original answer)
|
Thanks @Mttylzq! |
@ewartx yeah that worked beautiful! thanks, |
I read this solution from another site. Mine is the Xcode problem. I have to agree with the xcode license (
|
so much thx, @drewbrolik |
Thanks so much! @drewbrolik |
Thank thank you @drewbrolik :D |
$ sudo gem install -n /usr/local/bin compass |
Not familiar with compass but I've just upgraded to High Sierra and |
@drewbrolik was the good one for me (y) |
I upgrade to High Sierra a couple of days ago, and after doing so, I found that @duylinh : I attempted your method, it ran through a lengthly list of items it installed. I entered, "pod install" and I get the message: [ ! ] No 'Podfile' found in the project directory. @drewbrolik 's fix seems to have resolved the issue. Thank you. |
duylinh's solution worked for me but I got this error after gem update --system See: https://stackoverflow.com/questions/47171570/can-not-install-cocoapods-with-rubygem-2-7-1 running it (gem update --system) again came back with no errors and I proceeded. After that pod install worked. This was on High Sierra |
I encountered the same as @nfranzmeier but on macOS 10.14.3 Mojave. Second time no error and got the message "Latest version already installed. Done." |
I had this same issue while trying to use |
Hi @ifeoluwa-paystack I am having the same problem after upgrading to catalina. Can you post the solution? Thanks |
Hi @fxgx99, it's Ifeoluwa with a different account. What worked for me was running I do not know if it's related but before I did this, I installed the xcode command line tools. I had to do that when I updated from Sierra to High Sierra and from High Sierra to Mojave so it was the first thing I did before anything else.
|
I am getting the same error message as the one in your post above. Except when I do And when I do |
@fxgx99, you need to run the command as super user, I forgot to mention. It appears you have the command line tools installed so you do not need to run the |
Sorry I forgot to mention that I am running the |
Hi @alechp unfortunately it still doesn't work. I "think" that I am struggling to link colorls to the 2.6 ruby version which comes with Catalina. Because the error message actually says the 2.3 version is no longer there. The installation must have removed it. Below is the screenshots of my error messages: Any help will be appreciated |
I finally found a solution: so here is my solution for Catalina upgrade issue: I decided to reinstall everything: Install rvm from terminal: And voila.... |
on macOS Catalina works too for me |
Same for cocoapods:
|
Hi can fix for this, i tried every thing |
I hackily fixed this issue by manually editing the |
Run below command |
This link and all of the above helped me solve this. Thanks! |
Whenever a compass command is run on the command line, I get this error:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby: bad interpreter: No such file or directory
The text was updated successfully, but these errors were encountered: