From owner-freebsd-current Sun Sep 1 22:40:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA13301 for current-outgoing; Sun, 1 Sep 1996 22:40:26 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA13295 for ; Sun, 1 Sep 1996 22:40:24 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id BAA04383; Mon, 2 Sep 1996 01:39:28 -0400 (EDT) Message-Id: <199609020539.BAA04383@whizzo.transsys.com> X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol To: Michael Hancock cc: Kim Culhan , current@FreeBSD.org From: "Louis A. Mamakos" Subject: Re: Current build failure References: In-reply-to: Your message of "Mon, 02 Sep 1996 09:51:43 +0900." Date: Mon, 02 Sep 1996 01:39:27 -0400 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > 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