Date: Mon, 1 Nov 2004 18:50:42 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Peter Losher <Peter_Losher@isc.org> Cc: freebsd-current@freebsd.org Subject: Re: breakage upgrading from 5.3-RC1 to 5.3-RELEASE Message-ID: <20041101184843.S56441@carver.gumbysoft.com> In-Reply-To: <200410311550.58098.Peter_Losher@isc.org> References: <1098785643.67570.44.camel@localhost.netability.ie> <20041029101250.A21500@carver.gumbysoft.com> <200410311550.58098.Peter_Losher@isc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 31 Oct 2004, Peter Losher wrote:
> On Friday 29 October 2004 10:15 am, Doug White wrote:
> > This is indicative of your system clock being off by large amounts, or
> > reset timestamps on src/ files. Check the system date and correct.
> >
> > Cleaning up from that is not easy, though; you may have to remove and
> > re-extract your source. It will update files in the wrong way and
> > damage your tree.
> >
> > You can try 'make cleandir; make cleandir' and removing /usr/obj
> > completely if reconstiuting your source tree is painful.
>
> On both systems, the clock was off by less than a minute (46 seconds on
> on, the other 39 seconds), I ran ntpdate, then did a 'make cleandir; make
> cleandir' as well as removing /usr/obj and then later /usr/{obj,src},
> and checked out a fresh RELENG_5_3 src tree, and the same thing still
> happens.
>
> Ideas? - Peter
Try make OSRELDATE=0 buildworld I guess ... try the mega-botstrap. If that
doesn't do it then your build environment is seriously damaged.
Fixing the broken clocks and cvsupping from scratch fixed it for me on one
machine. If that doesn't do it then I don't know what to say other than
reformat & reinstall.
--
Doug White | FreeBSD: The Power to Serve
dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041101184843.S56441>