Set default stdlib requirement to mkl

[ZzEeKkAa]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [x] 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)
• [x] Ensured the license file is being packaged.

As mentioned by @h-vetinari at https://github.com/conda-forge/intel_repack-feedstock/pull/82/files/462540bf2bc86a600f7be112379d6def0ce68859#r1835172927 there was an error with setting correct glibc dependency

[ZzEeKkAa]

Thank you @h-vetinari for finding the issue. Could you please review this PR?

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

• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

[oleksandr-pavlyk]

Just making sure that change to replace - {{ c_stdlib }}_{{ target_platform }} >={{ c_stdlib_sycl_version }} # [linux] with - {{ c_stdlib }}_{{ target_platform }} {{ c_stdlib_sycl_version }} # [linux] was purely stylistic.

The real issue was that {{ c_stdlib_sycl_version }} was used in non-SYCL components, i.e., mkl.

[ZzEeKkAa]

Just making sure that change to replace - {{ c_stdlib }}_{{ target_platform }} >={{ c_stdlib_sycl_version }} # [linux] with - {{ c_stdlib }}_{{ target_platform }} {{ c_stdlib_sycl_version }} # [linux] was purely stylistic.

The real issue was that {{ c_stdlib_sycl_version }} was used in non-SYCL components, i.e., mkl.

Yes, exactly. I've checked that removing >= does not affect result glibc pinning