ENH add gcc930 migration by hand

[beckermr]

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 code>@<space/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.

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

For recipe:

• It looks like the 'libblas' output doesn't have any tests.
• It looks like the 'libcblas' output doesn't have any tests.
• It looks like the 'liblapack' output doesn't have any tests.
• It looks like the 'liblapacke' output doesn't have any tests.
• It looks like the 'blas-devel' output doesn't have any tests.
• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[beckermr]

@conda-forge-admin rerender

[beckermr]

xref: https://github.com/regro/cf-scripts/issues/1202

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