Date: Mon, 02 Sep 1996 01:39:27 -0400 From: "Louis A. Mamakos" <louie@TransSys.COM> To: Michael Hancock <michaelh@cet.co.jp> Cc: Kim Culhan <kimc@w8hd.org>, current@FreeBSD.org Subject: Re: Current build failure Message-ID: <199609020539.BAA04383@whizzo.transsys.com> In-Reply-To: Your message of "Mon, 02 Sep 1996 09:51:43 %2B0900." <Pine.SV4.3.93.960902093527.20202A-100000@parkplace.cet.co.jp> References: <Pine.SV4.3.93.960902093527.20202A-100000@parkplace.cet.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> Keep supping and making (once a week or once a day), current is often not > buildable. Ah, I thought that while current was on the bleeding edge, the code should certainly at least compile before it's checked in! Hard to imagine any good reason why it wouldn't complile, short of problems in the build environment. Heck, I feel stupid for actually *testing* the code I contributed - I didn't realize broken code was OK too. > If you're new to current track it for at least a couple of months > doing all of the above before posting to current. Yeah, I've been tracking -current for more than a year, and little of this advice actually seemed to be helpful. But maybe it's just me. I also had problems getting a just checked-out version -current to get very far through 'make world'. louie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609020539.BAA04383>