-
Notifications
You must be signed in to change notification settings - Fork 105
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
Install fails on macOS 15 #182
Comments
I'm getting the same issue but with less useful error messages.
|
I managed to get it to build by changing the Makefile from
I don't know why Based on rubygems/rubygems#1508 (comment) it looks like it comes from I was able to edit my
|
So is the solution to rebuild the ruby used by the gemset for the new system version (macOS 15.0 in my case)? Then gems should build ok as they'll use the same compiler right? |
For me rebuilding Ruby was the cause of the problem rather than the solution 😅 My timeline went something like this:
I'm sure there's a better way to do steps 3-5 there, or a bug in rbenv/ruby-build/ruby itself somewhere that will be fixed and make step 3 not result in a broken situation. To be clear, I don't think this is a sassc bug, it's just happened for sassc because it's the only C++ native extensions gem I'm using. |
It looks like a new version of "Command Line Tools for Xcode" just released and might have fixed this 🤞
|
FWIW... none of these fixes worked for me. (I'm running macOS 15.0.1 on a M1 Studio Ultra, with Xcode command line tools 16.0) |
It worked for me after installing llvm and updating
Mine is an Intel Mac running Sequoia 15.1. If you are running Apple Silicon, you will need to change the path to whatever |
None of them worked for me, (macOs Sequoia Version 15.1.1 (24B91) - Apple M2 Pro) please let me know if you have any idea. |
On Apple Silicon MBPro
brew install llvm
export PATH="/opt/homebrew/opt/llvm/bin:$PATH"
export LDFLAGS="-L/opt/homebrew/opt/llvm/lib"
export CPPFLAGS="-I/opt/homebrew/opt/llvm/include" I use
|
Thank you, @kaoru. This saved my day :)
In my case, it was fixed by updating the |
In case this is useful to someone, most of the above didn't work for me, but this did:
|
The text was updated successfully, but these errors were encountered: