From owner-cvs-src@FreeBSD.ORG Sun May 20 23:08:39 2007 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD45F16A473; Sun, 20 May 2007 23:08:39 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp7.server.rpi.edu (smtp7.server.rpi.edu [128.113.2.227]) by mx1.freebsd.org (Postfix) with ESMTP id 74D4613C4AD; Sun, 20 May 2007 23:08:39 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp7.server.rpi.edu (8.13.1/8.13.1) with ESMTP id l4KN8bSC025788; Sun, 20 May 2007 19:08:38 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20070520062748.GA54935@rambler-co.ru> References: <200705190756.l4J7u9wP058382@repoman.freebsd.org> <20070519085103.GA61276@rambler-co.ru> <20070519105804.6b6cae10@kan.dnsalias.net> <20070520062748.GA54935@rambler-co.ru> Date: Sun, 20 May 2007 19:08:37 -0400 To: Ruslan Ermilov From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-RPI-SA-Score: undef - spam scanning disabled X-CanItPRO-Stream: default X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.227 Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Scott Long , cvs-all@FreeBSD.org, Colin Percival Subject: Re: cvs commit: src/gnu/usr.bin/cc/cc_tools Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 23:08:39 -0000 At 10:27 AM +0400 5/20/07, Ruslan Ermilov wrote: > >It sometimes happens when the date/time are not being set >properly, so that the tools are mistakenly rebuilt again >at an inappropriate time when in the foreign environment >of the target -- the problem is usually understood better >when building for another CPU architecture and hitting it. >I think this was an inappropriate commit to make, unless >the problem can be reproduced. I have upgraded several >i386's and amd64's without a problem. Is there any way we could detect the clock-skew problem? This keeps coming up, year-after-year, for many different people, including very experienced developers. And when it does come up, it is either: (1) totally safe, and thus unnoticed, or (2) screws up someone in the middle of some major upgrade, thus causing great angst and gnashing of teeth. It would be nice if we could come up with a reliable check for the problem. -- Garance Alistair Drosehn = drosehn@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA