-
-
Notifications
You must be signed in to change notification settings - Fork 41
clangdev 17.0.0.rc2 #238
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
clangdev 17.0.0.rc2 #238
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
|
It's a bit concerning that the bump in GCC minimum revealed that apparently we've been using GCC's libstdcxx that must be somewhere in the MacOS image (presumably in the SDK?). Not sure if this was a recent change in llvm, but the fact that 17.0.0.rc1 passed (before llvm/llvm-project@5ddfea3 arrived with rc2) and then rc2 failed based on the detected libstdcxx version means we don't immediately know how far back this goes. Failure looks like: Comes from here. CC @conda-forge/clangdev |
|
Another aspect of libcxx dropping support for MacOS<10.13: just running clang is not compatible with 10.9 anymore: This happens with libcxx 17 here, but I don't actually understand how that can get pulled into the test env at all, as it has an explicit constraint for |
…nda-forge-pinning 2023.08.09.23.48.41
No description provided.