Skip to content
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

make flang a cross-compiler #63

Closed
h-vetinari opened this issue Aug 2, 2024 · 4 comments
Closed

make flang a cross-compiler #63

h-vetinari opened this issue Aug 2, 2024 · 4 comments

Comments

@h-vetinari
Copy link
Member

From discussion in #61; this already came up in #28, where we descoped this at the time. This question is about how to do this practically.

Main question I see is how we want to name the feedstocks:

  1. flang-feedstock for implementation; flang-activation-feedstock for activation
  2. flang-impl-feedstock for implementation; flang-feedstock for activation

The GCC compilers follow more 1. (ctng-compilers & ctng-compiler-activation), but gfortran on osx follows more 2. (gfortran_impl_osx-64 & gfortran_osx-64). I don't really mind either way.

It would probably be convenient to do this as of flang 19, because then we don't have to deal with fortran_main (llvm/llvm-project@8d53866), but if we could do 18 already, that would probably help the emscripten-folks.

Any preferences for naming @isuruf?

@isuruf
Copy link
Member

isuruf commented Aug 2, 2024

I prefer 1.

@h-vetinari
Copy link
Member Author

OK, thanks for the quick response. Do you have a preference to try 18 first, or go straight to 19?

@isuruf
Copy link
Member

isuruf commented Aug 2, 2024

Let's go straight to 19

@h-vetinari
Copy link
Member Author

Got a PR to staged recipes: conda-forge/staged-recipes#27470

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants