Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running
version_git.sh
to buildversion_git.jl
, we encode whether the current buildtree is modified. Unfortunately, this often runs in parallel with the eneration ofbuild_h.jl
, which means that more often than not,build_h.jl.phony
is sitting around in the build tree, and sincegit
hasn't been told to ignore that file, we get modified build trees a lot duringmake -jN
.We don't see this in final builds however, because when we swing back around in
make binary-dist
, the Makefile regeneratesversion_git.jl.phony
, checks it againstversion_git.jl
and notices thatgit
no longer things the build tree is dirty. (This being becausebuild_h.jl.phony
does not exist. Note that we never runmake binary-dist
in parallel). Thus, we always end up with aversion_git.jl
that identifies itself as coming from a pristine build, and the price we paid was just that we would always build the system image twice.This closes #27548