From aebd7702b5f34e3f9dccbbe687549ea6179c0557 Mon Sep 17 00:00:00 2001
From: carlislewishard <70146819+carlislewishard@users.noreply.github.com>
Date: Tue, 27 Jun 2023 10:31:35 -0400
Subject: [PATCH] Update README.md

fixed link to clone repo, also added in cmake flags for gfortran
---
 README.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 3671832cb..e011b8430 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ Parallelization in Swiftest is done with OpenMP. Version 3.1.4 or higher is nece
 The easiest way to get Swiftest on your machine is to clone the GitHub repository. To do so, open a terminal window and type the following:
 
 ```
-$ git clone https://github.itap.purdue.edu/MintonGroup/swiftest.git
+$ git clone https://github.com/carlislewishard/swiftest.git
 ```
 
 If your cloned version is not already set to the master branch:
@@ -85,7 +85,7 @@ CMake allows the user to specify a set of compiler flags to use during compilati
 
 As a general rule, the release flags are fully optimized and best used when running Swiftest with the goal of generating results. This is the default set of flags. When making changes to the Swiftest source code, it is best to compile Swiftest using the debug set of flags. You may also define your own set of compiler flags. 
 
-To build Swiftest with the release flags (default), type the following:
+To build Swiftest with the release flags (default) using the Intel fortran compiler (ifort), type the following:
 ```
 $ cmake ..
 ```
@@ -97,6 +97,11 @@ To build with another set of flags, simply replace ```DEBUG``` in the above line
 
 Add ```-CMAKE_PREFIX_PATH=/path/to/netcdf/``` to these commands as needed.
 
+If using the GCC fortran compiler (gfortran), add the following flags:
+```
+cmake -DCMAKE_Fortran_FLAGS="-I/usr/lib64/gfortran/modules/ -ffree-line-length-512" ...
+```
+
 After building Swiftest, make the executable using: 
 
 ```