Closed mathomp4 closed 2 years ago
Note that I did test this in a build and it...built. I don't know how to run this executable, but since all that changed was how CMake tries to build it, I can't see that it wouldn't be zero-diff. So I'm labeling it as so.
So this is a fun one. In testing the ADAS a while back, @bena-nasa every so often encountered a what looked like a race condition in the build. You'd build it once, it'd fail; build again serially, it worked.
Then, last night, my nightly build of GEOSadas saw this:
This was odd since there is only one
satinfo_util
module in the GEOSadas! After consulting with @tclune we found the issue. Themake_pcscaling.x
add_executable
is asking forsatinfo_util.F90
as a source:and it is a source, so nothing wrong there! The problem is that if you juuuust happen to build building that module at the same time it's building, say,
make_ozinfo.o
which also usessatinfo_util
then it could see an "incomplete" modulefile.It turns out @tclune and @bena-nasa actually figured this out a while back (see https://github.com/GEOS-ESM/GEOSana_GridComp/pull/36/commits/e16759e77b0b1b973a4e502a8de514743e981e43) and created the "libmksi" library to handle it.
So, we just apply the same fix here and make
make_pcscaling.x
depend on libmksi to getsatinfo_util
.