From owner-freebsd-current Fri Jun 7 10:02:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01987 for current-outgoing; Fri, 7 Jun 1996 10:02:52 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA01938; Fri, 7 Jun 1996 10:02:44 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA29627; Fri, 7 Jun 1996 11:02:39 -0600 Date: Fri, 7 Jun 1996 11:02:39 -0600 From: Nate Williams Message-Id: <199606071702.LAA29627@rocky.sri.MT.net> To: "Karl Denninger, MCSNet" Cc: hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org Subject: Build times (was Re: The -stable problem: my view) In-Reply-To: References: <199606071015.MAA00708@allegro.lemis.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A full build on a lightly-loaded P166 now requires nearly three hours, > and that's too long for a SUP which only changes two files! If you are familiar with the build process, then you *don't* have to run a 'make world' everytime. Someone as familiar with system builds should be able to figure out the effects of changed files, but unfortunately this means you need to baby-sit the SUP update files to determine what changed instead of simplying firing off a make world after every update. I *never* run a make world, and rarely even run a global make, but when things do change I will do the necessary individual steps in a make world to bring my system back into 'make world' status. Nate