On Nov 27, 2012, at 1:22 PM, Andrew Pinski <pins...@gmail.com> wrote: > On Tue, Nov 27, 2012 at 12:55 PM, Mike Stump <mikest...@comcast.net> wrote: >> This: >> >> Verify that you have permission to grant a GFDL license for all >> new text in tm.texi, then copy it to ../../gcc/gcc/doc/tm.texi. >> make[3]: *** [s-tm-texi] Error 1 >> make[3]: *** Waiting for unfinished jobs…. >> >> is one of the stupidest build errors I've seen all decade. Can someone fix >> it please? > > This means someone edited gcc/doc/tm.texi.in and/or gcc/target.def > without checking a new version of gcc/doc/tm.texi . > This build failure is to make sure we are not violating the rules > setup by FSF for the licensing for target.def both GPL and GFDL.
A review of the change and approval of the change should be enough to catch issues going into the FSF tree. The build should just copy the generated file to the source tree, if changed. The build failed for me, which is wrong, as there if absolutely no change I can make that runs afoul of copyright law, save copying in content for which would be a violation, which is completely uncatchable, so, there is absolutely no way to check for this failure and absolutely every other failure is a false positive, so, again, let me state that the check is wrong. What ever condition people are trying to catch, how they did it is wrong. I mean, we could have a check that fails the build if any source file has been modified. This would catch all new copyright volitions with probability 1; however, we don't do that? Why? Simple, too many false positives. By changing a file, you assert are doing so in a manner consist with law, and that is that. Once so asserted, there _can be_ no non-false positives, ever.
