-
-
Notifications
You must be signed in to change notification settings - Fork 47
llvmdev v14.0.0 #152
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
llvmdev v14.0.0 #152
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking a look so quickly!
bbb290e
to
1267631
Compare
no need to use two sources to work-around upstream issue 53281
b927554
to
ad06861
Compare
So, after removing the pin for macos SDK, we're at:
The upstream callsite is actually guarded on mac os 10.12 availability, but for some reasons this seems to misfire. |
That's fine then to use 10.12 SDK and 10.9 target. |
This reverts commit ad06861.
Thanks for the quick initial feedback @isuruf! This should be ready, PTAL @conda-forge/llvmdev |
Ping @conda-forge/llvmdev 🙃 Since this doesn't really contain anything controversial (and has already received some review in #143 and here), I'm planning to merge this in 48h unless there are comments to the contrary. |
c_compiler: # [win] | ||
- vs2019 # [win] | ||
cxx_compiler: # [win] | ||
- vs2019 # [win] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this needed? This would make downstream packages linking statically to do the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the (new) minimum to build LLVM 14: https://reviews.llvm.org/D114639
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the (new) minimum to build LLVM 14: https://reviews.llvm.org/D114639
@isuruf, any comment on this how you'd like to proceed with this?
Unsurprisingly I'm not ecstatic about trying to stem the tide here - I think the sane choice is to let vs2017 fade away. On top of that, it's not like clang is pervasively used on windows in our recipes, and we could stay on LLVM <14 for some time yet where necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fine. There are other issues with using VS2019. See MacPython/numpy-wheels#145
Thanks |
It is very likely that the current package version for this feedstock is out of date.
Checklist before merging this PR:
license_file
is packagedInformation about this PR:
@conda-forge-admin,
please add bot automerge
in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.Pending Dependency Version Updates
Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.
Dependency Analysis
We couldn't run dependency analysis due to an internal error in the bot. :( Help is very welcome!
This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/2026649665, please use this URL for debugging.