This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: stupid build error
On Tue, 27 Nov 2012, Mike Stump wrote:
> You failed to state a single case where a violation is caught.
It's not about catching violations of law, it's about catching cases where
the source tree is in an inconsistent state. And a not uncommon cause of
that is that someone didn't know about the relation between the three
source files, target.def, tm.texi.in and tm.texi, and modified tm.texi
directly, or modified multiple files by hand inconsistently. (Although
the code attempts to use timestamps to distinguish different cases of
inconsistency, this can be unreliable, especially if someone checked in an
inconsistent state and someone else is building from a tree updated with
svn update. So the rule is that in any case of an inconsistency in the
source tree, things are passed back to the user to make a determination,
based on examining the differences, of how to restore consistency to the
source tree - and of whether the resulting patch submission will need
docstring relicensing review.)
--
Joseph S. Myers
joseph@codesourcery.com