Date: Sun, 20 May 2007 19:08:37 -0400 From: Garance A Drosehn <gad@FreeBSD.org> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Scott Long <scottl@FreeBSD.org>, cvs-all@FreeBSD.org, Colin Percival <cperciva@FreeBSD.org> Subject: Re: cvs commit: src/gnu/usr.bin/cc/cc_tools Makefile Message-ID: <p06240805c27683e3c36d@[128.113.24.47]> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06240805c27683e3c36d>