From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30332 invoked by alias); 10 Dec 2012 22:57:59 -0000 Received: (qmail 30248 invoked by uid 48); 10 Dec 2012 22:57:42 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/55243] STAMP variable is not defined in t-avr Date: Mon, 10 Dec 2012 22:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-12/txt/msg01048.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55243 --- Comment #20 from Georg-Johann Lay 2012-12-10 22:57:41 UTC --- (In reply to comment #19) >> It works with read-only sources, provided everything is consistent. Or are >> you saying that a t-snip must not use $(STAMP)? > > I'm saying that the build process should never touch the source tree. Isn't ./gcc/doc/md.texi both in the repo and generated (from ./gcc/doc/md.texi.in)? And, if parts of the docs are changed you will we nagged to verify GFDL and to copy the new, auto-generated parts in place? >> Actually, the PR boils down to the fact the STAMP is not defined, I am not >> sure if the compiler is supposed to build without STAMP. > > Probably not, but what I'm trying to understand is why we seem to be fiddling > with the source tree when building the gnattools. As far as gnattools are concerned, it makes no difference whether the auto-generated files are stamped and written to $build or stamped and written to $source. I agree that the $source vs. $build matter should be cleaned up. However, that won't help with this PR because the rules and the dependencies and the needed tools will remain the same.