[DEBUG] clang exception issue

[xylar]

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.

[xylar]

This is just a test PR to see if I can make any headway on #65

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

[xylar]

@conda-forge-admin, please rerender

[conda-forge-admin]

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:

• The feedstock has no .ci_support files and thus will not build any packages.

[xylar]

@conda-forge-admin, please 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.

[conda-forge-admin]

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:

• The feedstock has no .ci_support files and thus will not build any packages.

[xylar]

@conda-forge-admin, please 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.

[xylar]

@conda-forge-admin, please rerender

[conda-forge-admin]

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:

• The feedstock has no .ci_support files and thus will not build any packages.

[conda-forge-admin]

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/conda-forge-webservices/actions/runs/11356598029.}

[xylar]

@conda-forge-admin, please 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.

[xylar]

It seems like the new hdf5 in #65 is likely responsible. It seems like we should create a small reproducer and add it as a (proposed) test at https://github.com/conda-forge/hdf5-feedstock

I'm not super good with this kind of thing but I'll give it a go if no one more proficient in c++ and/or hdf5 can do this. I probably won't get a chance to work on this further until this weekend.

[gillins]

Thanks @xylar let me know how you go. I could look at this next week if you don't get to it.

[xylar]

@gillins, I wasn't able to get to this this weekend (and won't in the remaining few hours). If you happen to have time, that would be wonderful. Otherwise, I'll see if I can find the time next weekend.

[gillins]

Thanks @xylar, I'll try and have a look. But - I just saw this: conda-forge/hdf5-feedstock#233 - seems lots of things have been addressed (https://github.com/HDFGroup/hdf5/blob/hdf5_1_14_5/release_docs/RELEASE.txt). Perhaps we should wait for this? How would we test this when it is merged?