gh-110704: Recommend distclean target over clean when source tree is not clean#112610
Conversation
distclean target over clean when source tree is not cleandistclean target over clean when source tree is not clean
|
This PR is stale because it has been open for 30 days with no activity. |
|
@gpshead, you made changes in that line. Could you please review this change? |
|
GH-150342 is a backport of this pull request to the 3.15 branch. |
|
GH-150343 is a backport of this pull request to the 3.14 branch. |
|
GH-150344 is a backport of this pull request to the 3.13 branch. |
…ce tree is not clean (GH-112610) (#150342) gh-110704: Recommend `distclean` target over `clean` when source tree is not clean (GH-112610) Recommend `distclean` target over `clean` when source tree is not clean (cherry picked from commit 3463105) Co-authored-by: James <6125322+SnoopJ@users.noreply.github.com> Co-authored-by: Gregory P. Smith <greg@krypto.org>
…ce tree is not clean (GH-112610) (#150343) gh-110704: Recommend `distclean` target over `clean` when source tree is not clean (GH-112610) Recommend `distclean` target over `clean` when source tree is not clean (cherry picked from commit 3463105) Co-authored-by: James <6125322+SnoopJ@users.noreply.github.com> Co-authored-by: Gregory P. Smith <greg@krypto.org>
…ce tree is not clean (GH-112610) (#150344) gh-110704: Recommend `distclean` target over `clean` when source tree is not clean (GH-112610) Recommend `distclean` target over `clean` when source tree is not clean (cherry picked from commit 3463105) Co-authored-by: James <6125322+SnoopJ@users.noreply.github.com> Co-authored-by: Gregory P. Smith <greg@krypto.org>
|
|
|
Closes #110704
This changeset recommends using the
distcleantarget over thecleantarget when the clean source tree check fails, as the latter does not remove files that will reliably fail the check if they are present (python$(BUILDEXE)in particular). Theclobbertarget might work just as well, butdistcleanseems like the more user-legible change here.Discovered while trying to run the build script introduced by #112473, I have not previously run into this problem before, but it had my scratching my head for a couple of minutes before I looked at the check target and realized the report was misleading me.
This change seems niche enough not to require a
NEWSentry but I'm happy to write one if a maintainer disagrees.