-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
use flang18 not flang5 #82
base: main
Are you sure you want to change the base?
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.04.16.14.02.35
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know enough to make a decision. Can you perhaps link to downstream packages this is affecting?
Perhaps it makes the most sense to check in with doing this conda-forge-wide: conda-forge/conda-forge-pinning-feedstock#1359
Sure, I'll give it a shot. Using
Returns only However, when I search for the packages relying on So maybe there aren't any cf packages for windows that depends on
Yes, that's a good idea. I'll make a post there as soon as I am confident that LLVM Flang is ready. We're still working out some kinks in compiling HDF5 with fortran enabled for windows using Flang. I was thinking if Scotch for windows is not used by any known packages on conda-forge, then maybe it would be good candidate for further testing of Flang? That way we could also try to build mumps-seq for windows against scotch. I'm currently in no rush, so feel free to take your time to consider this proposal :) |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.04.18.15.24.04
I propose moving from flang v5 to flang v18 in order for downstream packages to compile using flang v18
Checklist
conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)