Rerender feedstock in an attempt to fix #1

[pbeaucage]

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.

[conda-forge-webservices]

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.

[pbeaucage]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/libnpp-feedstock/actions/runs/6065595040.

[pbeaucage]

For context, I believe we might just have a corrupt build from patchelf 0.18.0, see for example here

Hopefully a rerender will change the package versions in the build chain and fix this without further intervention, though there are other options discussed (conda/conda-build#4881, conda-forge/cuda-cudart-feedstock#10, conda-forge/cuda-cudart-feedstock#11)

[jakirkham]

Thanks Peter! 🙏

Appreciate you taking the time to look

Think this is resolved with the fixes noted in comment ( #2 (comment) )

Also it appears recent cyrsoxs CUDA 12 builds are working with libnpp ( conda-forge/cyrsoxs-feedstock#16 ), which confirms this is resolved

Going to go ahead and close this out, but please let us know if anything else comes up 🙂