Date: Sat, 22 Jan 2000 09:05:19 -0800 (PST) From: John Polstra <jdp@polstra.com> To: jasone@canonware.com Cc: current@freebsd.org Subject: Re: even more breakage in current Message-ID: <200001221705.JAA16332@vashon.polstra.com> In-Reply-To: <20000121162540.E27689@sturm.canonware.com> References: <20000121101157.A18956@dub.net> <20000121142251.D27689@sturm.canonware.com> <20000121154727.C43755@dragon.nuxi.com> <20000121162540.E27689@sturm.canonware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20000121162540.E27689@sturm.canonware.com>, Jason Evans <jasone@canonware.com> wrote: > > I often do a 'make includes' to be able to iteratively test changes. Once > I'm happy that the changes are sound, there is no way to assure that the > changes didn't cause a bootstrapping problem like this one. It's feasible to perform valid tests, but it requires some care and planning. Whenever you're changing a system header file, write it down. When you are done making changes, re-install the virgin unadulterated copies of those header files. In general, do your best to restore your system to a pristine state. Then test with make world. Yes, this is a pain. But it's a pain for one person instead of for several hundred. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001221705.JAA16332>