clang-compiler-activation v13.0.1

[h-vetinari]

Continuing from #69, since the version bot had an error:

Details

The recipe did not change in the version migration, a URL did not hash, or there is jinja2 syntax the bot cannot handle!

Please check the URLs in your recipe with version '13.0.1' to make sure they exist!

We also found the following errors:

 - migrations do not work on versions not specified with jinja2

I chose to add 13.0.1 without dropping 11.1 or 12.0, but that would be easily doable, of course. Also added myself to maintainers following this comment.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[h-vetinari]

Blockers (indentation denotes dependency; c.f. also list from 12.0.1):

• llvm-meta v13.0.1 llvm-meta-feedstock#14
• llvmdev v13.0.1 (redux) llvmdev-feedstock#140
  • openmp v13.0.1 (redux) openmp-feedstock#57
  • lld v13.0.1 (again) lld-feedstock#34
  • clangdev v13.0.1 clangdev-feedstock#163
    • libcxx v13.0.1 (redux) libcxx-feedstock#83
    • build for llvm 13 cctools-and-ld64-feedstock#49
    • compiler-rt v13.0.1 (redux) compiler-rt-feedstock#37

Additionally in the LLVM-space:

• mlir v13.0.1 mlir-feedstock#9
• Update to clang-13 clang-win-activation-feedstock#14

[h-vetinari]

@conda-forge-admin, please rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[h-vetinari]

@conda-forge-admin, please rerender

[h-vetinari]

@isuruf
This should be the final piece to land LLVM 13 - I used the same list of dependencies as for 12 & 11, so I don't think anything should be missing here. I propose decoupling the build-numbers for the different LLVM versions, see the last commit (but no strong opposition to keep incrementing globally either).

[h-vetinari]

Gentle ping @isuruf

[isuruf]

Thanks

[h-vetinari]

Woohoo, finally LLVM 13 is available! 🥳

[h-vetinari]

LLVM 14 should be a bunch closer to the upstream release, I'm hoping (most of the blocking feedstocks have LLVM 14 rc's building successfully already). 🙃