Allow "generic" BLAS builds with CUDA enabled

[mgorny]

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.

---

Reenable generic BLAS when CUDA is used (#177), and disable CUDA 11.8 while at it, as discussed in that bug.

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11975477750. Examine the logs at this URL for more detail.}

[h-vetinari]

since that commit came after the rerender, you didn't actually create any new jobs?

Also, for the time we're debugging this, you might want to inverse this condition (only build CUDA+non-MKL) to save CI resources.

[mgorny]

This doesn't affect available jobs — they were always there, they just terminate without building or producing any artifacts. And yes, that confused me too, so I've checked.

[h-vetinari]

Yeah, what happens is that some more complicated skip conditions don't get detected correctly by smithy (or are hard to specify so that this happens), which I guess is what happened here.

[hmaarrfk]

have you confirmed that it works locally on a larger machine with docker? Using the python build locally py script?

If so, Can you move to cirun so that we can run the Linux builds on the CI?

[mgorny]

have you confirmed that it works locally on a larger machine with docker? Using the python build locally py script?

No, I've built it using conda build directly, since I had a warm ccache for it. Building from scratch via Docker would take a few hours for me.

[mgorny]

This was also included in #293