# GitHub Action: Setup Fortran with Conda **URL:** \ **Category:** Announcements\ **Created:** [June 20, 2025, 9:59am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869 "2025-06-20T09:59:03Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 20, 2025, 9:59am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/1 "2025-06-20T09:59:03Z")
As discussed [here](https://fortran-lang.discourse.group/t/very-simple-ci-workflow-for-fortran-apps-using-conda/9867), I’ve created a GitHub Action for setting up Fortran compilers using Conda, inspired by [Conda + Fortran](https://degenerateconic.com/conda-plus-fortran.html). > **[GitHub - gha3mi/setup-fortran-conda](https://github.com/gha3mi/setup-fortran-conda)** > > Contribute to gha3mi/setup-fortran-conda development by creating an account on GitHub. - Supports `gfortran`, `ifx`, `flang` and `lfortran` compilers - `fpm` is installed by default - You can specify additional Conda packages using the `extra-packages` input. > **Example CI workflow** > > ```yaml > name: CI > > on: > push: > branches: [main] > pull_request: > branches: [main] > > jobs: > test: > runs-on: ${{ matrix.os }} > strategy: > fail-fast: false > matrix: > os: [ubuntu-latest, macos-latest, windows-latest] > compiler: [gfortran, ifx, lfortran, flang-new] > include: > - os: ubuntu-latest > extra-packages: "" # additional conda packages if needed > - os: windows-latest > extra-packages: "" # additional conda packages if needed > - os: macos-latest > extra-packages: "" # additional conda packages if needed > exclude: > - os: macos-latest > compiler: flang-new > - os: macos-latest > compiler: ifx > - os: windows-latest > compiler: lfortran > - os: windows-latest > compiler: flang-new > steps: > - name: Checkout repository > uses: actions/checkout@v4 > > - name: Setup Conda > uses: conda-incubator/setup-miniconda@v3 > with: > auto-update-conda: true > activate-environment: fortran > channels: conda-forge, defaults > > - name: Setup Fortran > uses: gha3mi/setup-fortran-conda@main > with: > compiler: ${{ matrix.compiler }} > platform: ${{ matrix.os }} > extra-packages: ${{ matrix.extra-packages }} > > - name: fpm test (debug) > run: fpm test --compiler ${{ matrix.compiler }} --profile debug --verbose > > - name: fpm test (release) > run: fpm test --compiler ${{ matrix.compiler }} --profile release --verbose > > ``` ---
**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\ **Post date:** [June 20, 2025, 10:32pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/2 "2025-06-20T22:32:33Z")
@Ali awesome, thank you for setting this up! Four compilers, beautiful. ---
**Author:** ![jorgeg](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/jorgeg/32/6835_2.png) [@jorgeg](https://fortran-lang.discourse.group/u/jorgeg)\ **Post date:** [June 20, 2025, 10:47pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/3 "2025-06-20T22:47:33Z")
the beauty of not depending on MPI haha my actions are so stupid because MPI becomes stupid! thanks for this, it is amazing ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 20, 2025, 11:20pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/4 "2025-06-20T23:20:19Z")
Thanks @certik @jorgeg! @certik, could you confirm whether `lfortran` on Windows currently has known issues, or if something else might be going wrong? ```auto Run fpm test --compiler lfortran --profile debug --verbose + mkdir build\dependencies BUILD_NAME: build\lfortran COMPILER: lfortran C COMPILER: cc CXX COMPILER: cc COMPILER OPTIONS: -fPIC C COMPILER OPTIONS: CXX COMPILER OPTIONS: LINKER OPTIONS: INCLUDE DIRECTORIES: [] + mkdir build\lfortran_1C9F1A78448FC13A + mkdir build\lfortran_68BEE2AA1F5C26E0 [0%] main.f90 + mkdir build\lfortran_1C9F1A78448FC13A\test\ + lfortran -c .\.\src\main.f90 -fPIC -J build\lfortran_1C9F1A78448FC13A -Ibuild\lfortran_1C9F1A78448FC13A -o build\lfortran_1C9F1A78448FC13A\test\src_main.f90.o [25%] main.f90 done. Compilation failed for object " src_main.f90.o " stopping due to failed compilation STOP 1 Error: Process completed with exit code 1. ``` Also, `flang` + `fpm` on Windows gives: ```auto Run fpm test --compiler flang-new --profile debug --verbose + mkdir build\dependencies BUILD_NAME: build\flang-new COMPILER: flang-new C COMPILER: clang CXX COMPILER: clang++ COMPILER OPTIONS: -fPIC C COMPILER OPTIONS: CXX COMPILER OPTIONS: LINKER OPTIONS: INCLUDE DIRECTORIES: [] + mkdir build\flang-new_1C9F1A78448FC13A + mkdir build\flang-new_68BEE2AA1F5C26E0 [0%] main.f90 + mkdir build\flang-new_1C9F1A78448FC13A\test\ + flang-new -c .\.\src\main.f90 -fPIC -module-dir build\flang-new_1C9F1A78448FC13A -Ibuild\flang-new_1C9F1A78448FC13A -o build\flang-new_1C9F1A78448FC13A\test\src_main.f90.o flang-new: error: unsupported option '-fPIC' for target 'x86_64-pc-windows-msvc' flang-new: error: unsupported option '-fPIC' for target 'x86_64-pc-windows-msvc' [25%] main.f90 done. flang-new: error: unsupported option '-fPIC' for target 'x86_64-pc-windows-msvc' Compilation failed for object " src_main.f90.o " stopping due to failed compilation flang-new: error: unsupported option '-fPIC' for target 'x86_64-pc-windows-msvc' STOP 1 Error: Process completed with exit code 1. ``` It looks like `-fPIC` isn’t supported on Windows for `flang`. Would it make sense to remove `-fPIC` from the default compiler options for `flang` on Windows in `fpm`? ---
**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\ **Post date:** [June 21, 2025, 1:27am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/5 "2025-06-21T01:27:47Z")
Basic things should work on Windows, but we require the MSVC linker for linking. Where is the test file that you use? I can try it out and see what is going on. ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [June 21, 2025, 2:18am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/6 "2025-06-21T02:18:58Z")
For the third time (at least) almost all my CD/CI tests are broken so this looks like worth trying. My initial goal with github CD/CI was to standardize all my repositories to use the same test file, where the test installs fpm and ford and doxygen and a compiler on different platforms and then builds documents into the gh\_page branch and runs fpm test for --profile debug and release; so yours looks very appealing as it does that for more compilers than I was doing anyway, at least for fpm test. I found I needed to be able to supply fpm options on a per-OS / per-compiler basis in a few cases which I did with response files, but you might want to show how to select fpm options just for a specific compiler; and how to run ford and place the results into gh-pages as well. Looks promising. Hope to try it soon; using conda might be much more stable and avoid the repeated breakage I have seen in methods. I was about ready to give up on github CD/CI as it seemed a constant maintenance problem. This looks like it might solve that. ---
**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\ **Post date:** [June 21, 2025, 3:35pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/7 "2025-06-21T15:35:06Z")
I will also add that if there is any updates w.r.t. the flags that `fpm` uses for `lfortran`, do let me know and I can take care of that ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 21, 2025, 10:39pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/8 "2025-06-21T22:39:56Z")
The test is simple and can be found under [src](https://github.com/gha3mi/setup-fortran-conda/blob/main/src/main.f90) and [test](https://github.com/gha3mi/setup-fortran-conda/blob/main/test/check.f90), with the corresponding [fpm.toml](https://github.com/gha3mi/setup-fortran-conda/blob/main/fpm.toml) file provided. Here is an example of the test result: [GitHub Actions](https://github.com/gha3mi/setup-fortran-conda/actions/runs/15799987201/job/44536971502). ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 21, 2025, 10:59pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/9 "2025-06-21T22:59:43Z")
> [@urbanjost](#): > > Looks promising. Hope to try it soon; using conda might be much more stable and avoid the repeated breakage I have seen in methods. I was about ready to give up on github CD/CI as it seemed a constant maintenance problem. This looks like it might solve that. Thanks, @urbanjost! I hope that by adding more scenarios and tests, `setup-fortran-conda` can cover more situations and better support a variety of requirements. > [@urbanjost](#): > > where the test installs fpm and ford and doxygen and a compiler on different platforms and then builds documents into the gh\_page branch I’ve added support for `ford` and `doxygen` in the `dev` branch. After some testing, I plan to merge it into the `main` branch. You can see the workflow here: [https://github.com/gha3mi/setup-fortran-conda/blob/dev/.github/workflows/Doc.yml](https://github.com/gha3mi/setup-fortran-conda/blob/dev/.github/workflows/Doc.yml) > [@urbanjost](#): > > I found I needed to be able to supply fpm options on a per-OS / per-compiler basis in a few cases which I did with response files, but you might want to show how to select fpm options just for a specific compiler I see two possible approaches without using response files: 1. **Create separate jobs** for each OS/compiler combination in the workflow file (which might lead to a lot of duplication). 2. **Use a single workflow** with a matrix strategy, as shown here: [https://github.com/gha3mi/setup-fortran-conda/blob/dev/.github/workflows/CI.yml](https://github.com/gha3mi/setup-fortran-conda/blob/dev/.github/workflows/CI.yml). In the matrix, you can define any variables you need. I’ve added flags for both `debug` and `release` profiles for example, and I’m using the `include` feature to handle specific OS/compiler combinations. This matrix-based setup hasn’t been merged into the `main` branch yet. Alternatively, you can still use response files with `setup-fortran-conda`. The following pattern should work: `fpm @--`. With supported matrix values: ```auto os: [ubuntu-latest, macos-latest, windows-latest] compiler: [gfortran, ifx, lfortran, flang-new] ``` ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 21, 2025, 11:30pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/10 "2025-06-21T23:30:25Z")
Could you please check this test with `flang-new`? ```auto program check #if defined(TEST) print *, "This is a test" #endif end program ``` with `fpm test --compiler flang-new --flag "-DTEST"`, gives: ```auto ./test/check.f90:2:12: error: excess characters after expression #if defined(TEST) ^^^^^^ Compilation failed for object " test_check.f90.o " stopping due to failed compilation STOP 1 ``` It seems that when using `flang-new`, fpm requires the `-cpp` flag to be passed manually `fpm test --compiler flang-new --flag "-cpp -DTEST"`. This isn’t the case for other compilers. ---
**Author:** ![RonShepard](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@RonShepard](https://fortran-lang.discourse.group/u/RonShepard)\ **Post date:** [June 22, 2025, 4:05am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/11 "2025-06-22T04:05:09Z")
> [@Ali](#): > > This isn’t the case for other compilers. Most compilers adopt the convention that if the file extension is .f90, then no preprocessing occurs, and if the file extension is .F90, then preprocessing does occur. ---
**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\ **Post date:** [June 22, 2025, 9:46am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/12 "2025-06-22T09:46:19Z")
Great - would you please open an Issue on the `fpm` repository? Let’s check the `flang` documentation, CLI commands are mostly similar to those of GCC so maybe we should only add `-cpp` as default cpp pre-processing flag for flang as well. ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 22, 2025, 10:20am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/13 "2025-06-22T10:20:10Z")
[https://github.com/fortran-lang/fpm/issues/1155](https://github.com/fortran-lang/fpm/issues/1155) ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [June 22, 2025, 3:44pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/14 "2025-06-22T15:44:09Z")
Just a note that I get a warning ```plaintext Installing base environment... Preparing transaction: ...working... done Executing transaction: ...working... done Warning: entry_point.py:256: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. entry_point.py:256: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. installation finished. ``` It does not appear to cause any problem. ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 22, 2025, 5:21pm UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/15 "2025-06-22T17:21:27Z")
That warning isn’t directly from `setup-fortran-conda`. It’s coming from Conda itself, likely during environment setup when it extracts packages. ---
**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\ **Post date:** [June 23, 2025, 1:31am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/16 "2025-06-23T01:31:31Z")
Thanks. Simple code like that should work on Windows. It’s likely a missing MSVC linker. If this is an issue, we can eventually ship our own linker. ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [June 24, 2025, 3:40am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/17 "2025-06-24T03:40:34Z")
I got all the flang-new/gfortran/ifx cases working accept that the ifx one on windows tells me it cannot find ISO\_FORTRAN\_ENV. Anyone know how to resolve that? ```plaintext + mkdir build\ifx_EE9A1522C6DEBE16\M_time\ + ifx -c .\.\src\M_time __duplicate.f90 /Qdiag-error:10006 /check:all /error-limit:1 /Od /Z7 /assume:byterecl /free /module:build\ifx_EE9A1522C6DEBE16 -Ibuild\ifx_EE9A1522C6DEBE16 -o build\ifx_EE9A1522C6DEBE16\M_time\src_M_time__ duplicate.f90.o Intel(R) Fortran Compiler for applications running on Intel(R) 64, Version 2025.1.0 Build 20250317 Copyright (C) 1985-2025 Intel Corporation. All rights reserved. .\.\src\M_time__duplicate.f90(2): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [ISO_FORTRAN_ENV] use, intrinsic :: iso_fortran_env, only : stderr=>ERROR_UNIT ------------------^ .\.\src\M_time__duplicate.f90(1982): catastrophic error: Too many errors, exiting compilation aborted for .\.\src\M_time__duplicate.f90 (code 1) [0%] M_time__duplicate.f90 done. ``` I needed to skip the -fPIC switch on mswindows when using Fortran, as the executables would not run; set up the preprocessor and directives to conditionally skip anywhere using kind=real128 for flang-new, add the --cpp switch for lfortran and so on to the point where for me personally, a seperate script for each compiler+OS would be simpler, but your core setups let me test eight os/compiler combinations automatically. That adds two compilers to what I had running (flang-new and lfortran) and all mine had broken infrastructure accept the gfortran tests so this is very useful to me. I also like to have the status flags in the markdown either in README.md or a file just for that purpose in STATUS.md instead of using the github actions menu to quickly see pass/fail and I did not figure out how to do that with a file checking multiple compilers where I could see each compiler/OS combination so going to individual files lets me do that (does anyone know how to break a composit test into multiple flags?). As in [STATUS.md](https://github.com/urbanjost/M_time/blob/main/docs/STATUS.md) as a simple example ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 24, 2025, 4:52am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/18 "2025-06-24T04:52:42Z")
Thanks! Yes, I think it’s a linker problem. the same issue I see with the `ifx` on win. I haven’t resolved it yet, but I’ll give it a try this week! ---
**Author:** ![Ali](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ali/32/751_2.png) [@Ali](https://fortran-lang.discourse.group/u/Ali)\ **Post date:** [June 24, 2025, 7:37am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/19 "2025-06-24T07:37:34Z")
I forked your repository to use as a test case for CI. I believe I’ve resolved the issue related to: `Error in opening the compiled module file. Check INCLUDE paths. [ISO_FORTRAN_ENV]` However, there’s now a different error: ```auto test\test_suite_M_time.F90(187): error #6626: The name of the internal procedure conflicts with a name in the encompassing scoping unit. [PUT_ENVIRONMENT_VARIABLE] subroutine put_environment_variable(name,value,status) ``` Could you please take a look? [test CI · gha3mi/M\_time@5124937 · GitHub](https://github.com/gha3mi/M_time/actions/runs/15843929848/job/44661704291) I’ll review your valuable comments again to further improve the CI setup. ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [June 24, 2025, 9:58am UTC](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869/20 "2025-06-24T09:58:26Z")
Your fix worked; but I needed to add /fpp for ifx running in pure windows. I also had to use the pre-processor to call the Intel extensions equivalent to sleep(3c) and usleep(3c) which apparently are not available using icc(1) as the C co-compiler (it was the first time building that library in a pure MSWindows environment. Not usually a MSWindows user accept via Cygwin or ULS or Msys2 so had some other things to change technically unrelated to your CD/CI utility). So that worked. Thanks! The changes are in the [https://github.com/M\_time](https://github.com/M_time) repository. Now I need to sort through all that and tidy it up and then theoretically just copy it to the other fifty or so, as they are already set up to do a “fpm test” as their CD/CI process. Still not sure why I needed to make some of the changes for fpm to work. Did I have to turn off -fPIC on MSWindows or should I change the loader to use PIE or PIC, perhaps? I was surprised I had to explicitly add /fpp or -cpp instead of .F90 working as a flag to pre-process (although MSWindows is not case-sensitive in some respects, so maybe that is not a common convention in MSWindows?) and so on. So I will probably change CI.yml to be eight different simpler scripts I think; but use anything you find useful in it as it sits; as it is all public domain or has a very liberal MIT license. Since the example program and test framework M\_framework load a lot of other fpm repositories that is exercising quite a bit of code, so your setup of the environments is looking very good; I just need to sort through the fpm and compiler/loader issues that got raised as a result of your setup working! [Next page](https://fortran-lang.discourse.group/t/github-action-setup-fortran-with-conda/9869.md?page=2)