Rebuild with libcxx>=17

[saraedum]

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.

[saraedum]

@conda-forge-admin, please rerender

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-webservices]

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:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[saraedum]

@conda-forge-admin, please rerender

[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/meta.yaml) and found it was in an excellent condition.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[saraedum]

@wlav is cppyy-cling going to work with clang 16 with root 63202 patches?

I am running in more problems because we have updated the libcxx in macOS and I guess that using a more recent clang colud help.

[saraedum]

So, essentially this conda-forge/conda-forge-pinning-feedstock#4890 now breaks a lot of builds for me that depend on cppyy. On macOS, I am now forced to use libcxx>=17 but cppyy-cling forces libcxx<17 through the clangdev 13 package we are building against.

I think I'll have to disable macOS for the downstream packages of cppyy since it seems to be not usable here at the moment.

Any thoughts @isuruf?

[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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• No valid build backend found for Python recipe for package cppyy-cling using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[saraedum]

@conda-forge-admin, please rerender

[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/meta.yaml) and found it was in an excellent condition.

[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/cppyy-cling-feedstock/actions/runs/10527513648.

[saraedum]

@conda-forge-admin, please rerender.

[saraedum]

@conda-forge-admin, please rerender.

[saraedum]

@conda-forge-admin, please rerender.

[wlav]

@wlav is cppyy-cling going to work with clang 16 with root 63202 patches?

I am running in more problems because we have updated the libcxx in macOS and I guess that using a more recent clang colud help.

Upstream is at llvm16 (released), but is also very close to a release build on llvm18, so I was waiting on the latter. However, given these troubles, I'll start moving to llvm16 now.

[saraedum]

I managed to build this on macOS, I am not sure whether this is functional but maybe I am lucky.

[wlav]

I pushed the changed needed for LLVM16 into https://github.com/wlav/cppyy-backend/ . Still six failing tests on Linux. Haven't tried the other platforms yet.