-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to the latest compilers on conda-forge #94
Conversation
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 ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.08.23.18.51.20
The only issue is linking on osx (intel):
This issue happens with both 0.39.0 (which works with Clang 16) and 0.40.0, so it is caused by the upgrade of Clang from 16 to 17. Everything else seems to work. |
@conda-forge-admin, please rerender |
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/lfortran-feedstock/actions/runs/10541415336. |
Still the same linker error even after enforcing libcxx 17. |
Closing in favor of #102. |
Important: this requires using LLVM 17 on osx, but LFortran does not work with LLVM 17 yet (it compiles, but only a few tests work so far): lfortran/lfortran#4210. So this PR must stay a draft, until we fully support LLVM 17 in LFortran. Until then this PR is to ensure that at least the conda packages can be built on all platforms.
TODO:
__availability_version_check
with LLVM 17 on macOS Intel (osx-64) #96In the worst case, if we are blocked by the second issue, we can drop macOS / intel support, since eventually it will get dropped anyway once most people move on to Apple Silicon. The first issue however is a blocker. We need to fix that in LFortran first.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)