From owner-freebsd-current Fri Oct 31 12:14:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02267 for current-outgoing; Fri, 31 Oct 1997 12:14:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02261 for ; Fri, 31 Oct 1997 12:14:53 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id MAA23649; Fri, 31 Oct 1997 12:14:32 -0800 (PST) To: Simon Shapiro cc: John-Mark Gurney , freebsd-current@FreeBSD.ORG Subject: Re: More on LINT Kernel Failure to compile In-reply-to: Your message of "Fri, 31 Oct 1997 09:34:01 PST." Date: Fri, 31 Oct 1997 12:14:32 -0800 Message-ID: <23644.878328872@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Had I had to compile the LINT kernel, I know how to do it. The problem is > that I assumed (hate that word :-) that the LINT kernel is sort of standard > sanity check for sources and is supposed to compile all by itself, without > me ``assisting'' it. And this is entirely correct. It used to be incumbent on people to keep LINT in working order for exactly that reason and it's quite unfortunate that this has been slacked off on a bit in -current recently. It was never anyone's intention that a LINT kernel be bootable, but it was supposed to at least compile and, now that it doesn't, will be hiding any number of problems from detection in that manner. It should be fixed by whomever broke it last, to paraphrase Bruce. Jordan