Anthony Islas

Yes, though I haven't taken a look at the logs you posted in that issue the problem described matches the erroneous behavior pretty well. I suspect it may help, though...

Are you seeing these issues on either the latest updates from develop (9e265af51ddb41cd1993d55289e13a5bcb3ae0c4) or the current release candidate ([release-v4.6.0](https://github.com/wrf-model/WRF/tree/release-v4.6.0))? These now include build dependency fixes and syntax/flag updates for the...

I've taken a closer look at the issue, and as far as I can tell this is not a memory leak (though it does take an exorbitant amount of memory)...

Correct, `-O0 -no-ip` and ensuring the MPI compiler wrapper does not sneak any flags in as well

@weiwangncar Not exactly but it is in the same scope of issue - `NETCDF4_DEP_LIB` as it is written right now tries to do a lot of extra logic that `nc-config...

Going through PRs for v4.5.2, I realized #1923 should solve this. It also slightly addresses my previous point of better utilizing `nc-config --libs` as the main way to link in...

@mgduda These changes were made independent of #1923. Testing with current develop/master/ or where `release-v4.5.2` branches from develop should demonstrate the issues in the `test/nc4_test.log` logfile. As that PR was...

@weiwangncar I think that is fine

@weiwangncar Nope, no conflicts should arise from our respective changes in registry

I'd say this would be a nice-to-have if we can get it in, but not critical.