From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18062 invoked by alias); 4 Dec 2001 19:51:31 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 18020 invoked from network); 4 Dec 2001 19:51:28 -0000 Received: from unknown (HELO puce.csi.cam.ac.uk) (131.111.8.40) by sources.redhat.com with SMTP; 4 Dec 2001 19:51:28 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by puce.csi.cam.ac.uk with esmtp (Exim 3.22 #1) id 16BLb9-0000hH-00; Tue, 04 Dec 2001 19:51:23 +0000 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.12 #1 (Debian)) id 16BLb8-0006Sy-00; Tue, 04 Dec 2001 19:51:22 +0000 Date: Tue, 04 Dec 2001 11:51:00 -0000 From: "Joseph S. Myers" X-X-Sender: To: cc: , , , Subject: Re: Ada build now requires gnatmake? In-Reply-To: <200112041936.fB4JaiY29839@ulmo.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-12/txt/msg00149.txt.bz2 On Tue, 4 Dec 2001 guerby@acm.org wrote: > > I thought that the generated files were now mentioned in > > contrib/gcc_update, so if you update with that or use contrib/gcc_update > > --touch after updating you shouldn't see the problem. > > You'll get not-in-synch generated files, so you'll probably either > won't be able to build or build a non-functional compiler. It is my > understanding that gcc_update is intended just to make sure timestamp > are rights before making a release tarball, but it can't make sure > sources are right :). gcc_update --touch works on the following basis: * People checking in source files will check in files generated from them if there are any changes to the generated file (many changes to the source file may not cause such changes, in some cases), but CVS updates or applying patches might have left the timestamps in the wrong order even though the files are in fact up to date. * When a generated file is removed from CVS, it is also removed from gcc_update (otherwise it does indeed get touched wrongly and stay out of date). If, for example, "autoconf" on your PATH is 2.5x rather than 2.13, you need to use gcc_update or you'll get breakage from bogus attempts to regenerate configure scripts with a too-recent version. -- Joseph S. Myers jsm28@cam.ac.uk