Update crosstool_wrapper_driver_is_not_gcc

[ngam]

Minor updates following upstream.

Checklist

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

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

[ngam]

@conda-forge-admin, please rerender

[ngam]

@xhochy @wolfv could you please review and see if other changes are needed? These are minor, but I suspect more changes on the jaxlib and tensorflow ends require more updates here. I am having trouble tracing all of this down and updating this feedstock may help. Note a lot of changes took place on the jaxlib and tensorflow ends lately, especially on the front of updating things to c++17

xref:
conda-forge/tensorflow-feedstock#262
conda-forge/tensorflow-feedstock#261
conda-forge/tensorflow-feedstock#260
conda-forge/jaxlib-feedstock#122

[h-vetinari]

Any reason not to reset the patch version when bumping minor?

[ngam]

Good catch. No idea what I was doing! Do you think bumping the minor here is warranted anyway?

[h-vetinari]

Do you think bumping the minor here is warranted anyway?

No idea; I had assumed it was intentional. Something for @conda-forge/bazel-toolchain to decide...

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/bazel-toolchain-feedstock/actions/runs/2983160143.

[ngam]

Closing after weeks with no response...