You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the develop.md page, add a description of what compilers were used successfully to build FEHM.
Talk to George, Phil, and Xiang for their Windows builds, Erica knows which were used for V3.6 on linux, mac, and windows.
See also this email between George and Phil:
I got it running on my laptop even with the odd messages. My dispersion test problem for VEDAT runs great.
Looks like Visual Studio can interface with GIT.
From: george zyvoloski
Sent: Thursday, August 29, 2024 7:27 AM
To: Stauffer, Philip H
Subject: [EXTERNAL] Re: Any thoughts on this?
Hi Phil. My Intel compiler is a 2013 model with updates. It is stand-alone. Basically I don't know enough to comment. G
On Thu, Aug 29, 2024, 9:07 AM Stauffer, Philip H <[[email protected]](mailto:[email protected])> wrote:
Intel(R) Fortran Compiler Classic (ifort) is now deprecated and will be discontinued late 2024. Intel recommends that customers transition now to using the LLVM-based Intel(R) Fortran Compiler (ifx) for continued Windows* and Linux* support, new language support, new language features, and optimizations.
Feb 28, 2024
The text was updated successfully, but these errors were encountered:
This error shows up on Visual Studio when using a fortran compiler that doesn't support LLVM. To fix it,
Make sure you have "Release" and "x64" listed on the toolbar.
Go to "View" --> "Solution Explorer" --> "Properties (The little wrench icon)"
For "Use Compiler" select "inherit from project default" from the dropdown.
This should show "IFX" next to the FEHM name in the Solution Explorer menu. You are now set to build.
On the develop.md page, add a description of what compilers were used successfully to build FEHM.
Talk to George, Phil, and Xiang for their Windows builds, Erica knows which were used for V3.6 on linux, mac, and windows.
See also this email between George and Phil:
The text was updated successfully, but these errors were encountered: