build for MKL 2025.0

[h-vetinari]

Not having this pushes the solver into weird contortions like

- libblas                            3.9.0  25_win64_mkl           conda-forge        4MB
+ libblas                            3.9.0  25_win64_openblas      conda-forge        4MB
- libcblas                           3.9.0  25_win64_mkl           conda-forge        4MB
+ libcblas                           3.9.0  25_win64_openblas      conda-forge        4MB
- liblapack                          3.9.0  25_win64_mkl           conda-forge        4MB
+ liblapack                          3.9.0  25_win64_openblas      conda-forge        4MB

because it ends up prioritizing the newer MKL; apparently despite the track_features on the non-default BLAS impl here.

We might want to add more track_features here?

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

[h-vetinari]

This runs into problems due to conda-forge/libhwloc-feedstock#83 and (I think) wrong metadata in conda-forge/intel_repack-feedstock#82 (that is, unless MKL now requires 2.28 everywhere)

[ZzEeKkAa]

@conda-forge-admin rerender

[ZzEeKkAa]

win64 mkl build is still failing(

[ZzEeKkAa]

@mkrainiuk could you take a look?

[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). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

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

[h-vetinari]

Did some digging where the use of mkl_rt comes from - it's been there since the very beginning of windows support: bf90dd3

Furthermore, the MKL docs indicate that this should still work. I've asked again in conda-forge/intel_repack-feedstock#83

[stijn-vanesch]

What is the status of mkl >=2025 support? This is currently blocking for us as pytorch with xpu support (provided on intel channel) requires mkl>=2025 and opencv requires libblas

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• ❌ You're setting a constraint on the __osx virtual package directly; this should now be done by adding a build dependence on {{ stdlib("c") }}, and overriding c_stdlib_version in recipe/conda_build_config.yaml for the respective platform as necessary. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

[h-vetinari]

Almost a year later, the problems seem to have simply gone away... #150