-
Notifications
You must be signed in to change notification settings - Fork 451
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
1.0.86 producing clang: error: invalid version number in '-mmacosx-version-min=1.1'
on macos 10.14
#963
Comments
Uhh that's a new one. I'll try and see how 1.1 is getting passed there. That's definitely a bug with how low it is. @terakilobyte Do you set |
@BlackHoleFox we don't set anything ourselves. The specific dependency that is causing the issue is ring. However, changing versions doesn't change the outcome, and grepping the code doesn't show this value anywhere. The specific trace from cargo is
I also checked an env dump on the host and it's not being set there. |
I skimmed through ring's |
It seems likely that the crate hitting it is just a red herring. |
@terakilobyte Can you run |
@BlackHoleFox Here's the output from the host:
|
uhhhh weird. I'll look into that through this week. After downloading XCode 11.3.1 I don't even see that value in the SDKSettings JSON. |
These are mac stadium hosts and moving from 10.14 to 11 makes the issue go away, so it could be something specific to our setup. It's not blocking us so please don't burn the candle at both ends. |
Think I've figured the issue out here and a more robust solution. Gonna need a few days to find the time to implement it though apologies. |
I noticed that |
We build for a variety of platforms and noticed build failures on macOS 10.14,
clang: error: invalid version number in '-mmacosx-version-min=1.1'
. After investigating, we found that the issue is related to cc 1.0.86. Manually editing our lock file and pinning to 1.0.83 resolves the issue. We do not directly depend on cc.The text was updated successfully, but these errors were encountered: