BLD: Check for glibc symbols in redist binaries

[carterbox]

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.

In this PR, I have added a script developed by @mtjrider which checks for glib symbols in the shipped binaries.

In theory this means we don't have to match the glibc version with the os_version anymore, but let's get explicit permission from the channel before doing that. Brought this up at conda-forge core meeting. Response was good.

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

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

[carterbox]

Haha! It works!

[carterbox]

Note that it's not necessary to set the os_version if we are checking the binaries for glibc symbols.

[carterbox]

Gonna revert this until we get approval from conda-forge/core at a future meeting. Or maybe just wait until that meeting before merging this PR.

[carterbox]

Discussing this tomorrow at meeting.

[carterbox]

Feedback from core meeting what that checking symbols explicitly is better than testing if loading crashes the library.

[jakirkham]

Thanks Daniel! 🙏

We also have some dlopen tests in a few packages (below). Is this something we would want to capture here?

• nvcomp
• cuquantum
• cusparselt
• cutensor

[carterbox]

For clarity, if we were to add this test to cudnn it would not check if cudnn uses dlopen. It would only use dlopen to load cudnn? How is that better than link checking?

[carterbox]

@conda-forge-admin, please rerender

[carterbox]

Thanks Daniel! 🙏

We also have some dlopen tests in a few packages (below). Is this something we would want to capture here?

• nvcomp
• cuquantum
• cusparselt
• cutensor

This test already exists in this feedstock.