You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No. If it was not properly detected, the error would not be happening.
I don't have expertise with either Conda or MacOS packaging, but after talking with some people who do, here is what I think is happening
Conda targets ancient version of MacOS during compilation. 10.09 was released 2013 and the support ended in 2016.
Apple Clang checks whether specific features are available on the target version of MacOS and errors out if not. However, Clang assumes that it targets the system libc++. Conda builds and distributes its own libc++, but Clang does not know that.
The actual libc++ defines the feature availability macro to the correct value, and Catch2 tries using std::uncaught_exceptions.
Clang sees that, and because the system libc++ for MacOS 10.09 does not support std::uncaught_exceptions, it errors out.
The solution is to
Define _LIBCPP_DISABLE_AVAILABILITY during compilation.
Describe the bug
On macOS we're getting:
See conda-forge/catch2-feedstock#58
It could be that #1911 is not properly detected?
Expected behavior
Proper build and run.
Reproduction steps
https://github.com/conda-forge/catch2-feedstock/blob/main/recipe/meta.yaml
https://github.com/conda-forge/catch2-feedstock/blob/main/recipe/build.sh
https://github.com/conda-forge/catch2-feedstock/blob/main/recipe/run_test.sh
Platform information:
Additional context
The text was updated successfully, but these errors were encountered: