Rebuild 11.x with vs2017

[mbargull]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [x] Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

Trying to get a build with which llvmlite builds on Windows. See

• https://github.com/conda-forge/llvmlite-feedstock/pull/68#issuecomment-1292480034 ff
• https://github.com/conda-forge/llvmlite-feedstock/pull/68#issuecomment-1293550946

[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.

[jakirkham]

Thanks Marcel! 🙏

Let's give this a try. If this works, we should pull the LLVM 11.1 packages built with VS 2019

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[jakirkham]

Based on the discussion in this thread ( https://github.com/conda-forge/llvmlite-feedstock/pull/68#discussion_r1007167806 ). Sounds like this change wasn't needed in the end (and we may want to revert)

cc @isuruf

[mbargull]

Ah, sorry, forgot to add a comment here. I reverted on the branch directly, see https://github.com/conda-forge/llvmdev-feedstock/commit/ac359c547e7c8c21c2b2c9b21acc0e76fc2a87f7 .

[jakirkham]

No worries. Thanks Marcel! 🙏