Rebuild for flang 19

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update flang19.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

This package has the following downstream children:

• lapack
  and potentially more.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/11338327077 - please use this URL for debugging.}

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

Aside from the unix failures that I haven't looked at yet (seems some symlinks are broken...), AFAIU this would now need conda-forge/lapack-feedstock#76 to align the expected library library names.

[h-vetinari]

Just realized that we cannot support both openblas variants (openmp/pthreads) on windows with

blas-feedstock/recipe/meta.yaml

Lines 80 to 81 in 19dfccc

	run:
	- {{ pin_compatible("libopenblas", max_pin="x.x.x", exact=win) }} # [blas_impl == 'openblas']

So in a post-conda-forge/openblas-feedstock#115 world, we'll need to pin differently here, or more likely: build twice on windows.

[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/12370386826. Examine the logs at this URL for more detail.}

[h-vetinari]

Given that the solver gets pushed into ever-more bizarre corners over this (today I got an environment downgraded to mkl 2020), I'm going to skip the failing test here and move on for now. We're already skipping a whole bunch of tests on MKL, so three more are unlikely to be a game changer. I'll test this against SciPy 1.15 once it's released shortly.