Build a variant without features to use latest sysroot outside conda-build

[isuruf]

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.

[isuruf]

@conda-forge-admin rerender

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

• License exception is not an SPDX exception.

Documentation on acceptable licenses can be found here.

[beckermr]

I am 99% sure @mbargull said this kind of package would break bioconda builds. Maybe he can comment here?

cc @conda-forge/core for viz

[isuruf]

Not really. I checked and they use a cos7 based docker image, so they would still get sysroot_linux-64=2.17 by default

[beckermr]

How does that work? I guess the runtime constraint on glibc?

[isuruf]

I guess the runtime constraint on glibc?

Yes

[beckermr]

The other way we had wanted to work on this was to enable a "system" sysroot where our compilers would use whatever sysroot is available on the system itself.