# Gfortran on Windows for classroom setting

**URL:** <https://fortran-lang.discourse.group/t/gfortran-on-windows-for-classroom-setting/4478>\
**Category:** Help\
**Created:** [October 7, 2022, 7:09pm UTC](https://fortran-lang.discourse.group/t/gfortran-on-windows-for-classroom-setting/4478 "2022-10-07T19:09:48Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\
**Post date:** [October 7, 2022, 8:46pm UTC](https://fortran-lang.discourse.group/t/gfortran-on-windows-for-classroom-setting/4478/9 "2022-10-07T20:46:43Z")

</div>

> [@gnikit](#):
>
> Is that also the case with fortran-compilers?

This thread is relevant for the status of Fortran on conda-forge:

> [@Conda toolchain for Fortran on Windows](https://fortran-lang.discourse.group/t/3206):
>
> Just saw this post - very exciting! I contribute to both scipy and conda-forge (the latter more than the former), and the “best bet” for dealing with fortran (on windows; unix is doing fine with gfortan) we have currently is the upcoming flang(-in-LLVM). I think we’d be quite open to bump the fortran compiler (in conda-forge) aggressively if that’s required for building packages (and doesn’t unnecessarily remove old platform/ABI support). Anaconda does not have the same restrictions as conda-…

---

_[View the full topic](https://fortran-lang.discourse.group/t/gfortran-on-windows-for-classroom-setting/4478)._