Require GLIBC 2.17+ in MPI compilers

[jakirkham]

Fixes https://github.com/conda-forge/openmpi-feedstock/issues/143

Adds sysroot_{{ target_platform }} 2.17 to requirements/build of MPI compiler packages. This will make GLIBC 2.17 a minimum requirement at install time.

---

Checklist

• [x] 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)
• [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.

[conda-forge-webservices[bot]]

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.

[jakirkham]

How do we handle build number bumps for these packages?

[jakirkham]

We are already using sysroot above. This is just trying to fix a user problem

If someone wants to migrate this feedstock great, but please handle that separately

[beckermr]

Totally make sense @jakirkham. Indeed a separate PR is better! LGTM and thank you!

[jakirkham]

Marking as draft until we figure out how to handle the build/number here. Just want to make sure we handle that correctly

[beckermr]

What is the question about the build number specifically?

I'd argue we bump it to get a working build and also apply patches to the problematic older builds.

[leofang]

Thanks, @jakirkham, this looks good to me. Is there anything else needed before merging?

[jakirkham]

If the build number bump looks good, then this should be ready to go

[leofang]

Thanks, John!

[jakirkham]

Thanks Leo and Matt! 🙏

[jakirkham]

We should use the new stdlib stuff, right?

Handling the {{ stdlib('c') }} pieces in PR: https://github.com/conda-forge/openmpi-feedstock/pull/149