Michael Duda

@weiwangncar If you also approve this PR, I'll merge it to `develop` so the changes will appear in the WPS v4.7.0 release.

@veech I may be missing something, but I think the existing `Linux x86_64, gfortran` stanza in `configure.defaults` should work equally for `x86_64` and `aarch64`. I'd suggest creating a branch from...

@veech Apologies for the long delay in following up. It looks like the change that have been proposed in PR #262 should allow you to build with the GNU compilers...

After cleaning the build, it looks like the following processed source files aren't being removed: ``` external/RSL_LITE/feedback_domain_em_part1.f90 external/RSL_LITE/feedback_domain_em_part2.f90 external/RSL_LITE/force_domain_em_part2.f90 external/RSL_LITE/interp_domain_em_part1.f90 external/RSL_LITE/interp_domain_em_part2.f90 external/RSL_LITE/interp_domain_em_part3.f90 external/RSL_LITE/interp_domain_em_small.f90 ```

I don't recall whether WRF always uses the PR description as the merge commit message, but if so, perhaps it would be better to include a description of the code...

@islas Should we add the generated `inc/deallocs_*.F` files to a `.gitignore` file? Otherwise, these show up as untracked files after building. (Note, too, that we should do the same for...

> I see that there is a `.gitignore` in `inc/`, would `*.F` be better, or maybe just > > ``` > deallocs_*.F > allocs_*.F > ``` > > to the...

> `-V` is part of GNU sort, so I would recommend something like: `sort -t. -k 1,1.4n -k 2,2nr -k 3,3nr` to get the desired effect. The breakout into explicit...

I'm not sure whether the incorporation of the `-` character in the first key is too clever or not. So an alternative might be ``` sort -t. -k 1.5,1nr -k...

> > Still wonder why the some of the changed files are not related to the table change. > > @weiwangncar Those changes are due to the difference between the...