From owner-freebsd-current Fri Oct 31 11:13:42 1997 Return-Path: <owner-freebsd-current> Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28387 for current-outgoing; Fri, 31 Oct 1997 11:13:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28378 for <freebsd-current@freebsd.org>; Fri, 31 Oct 1997 11:13:39 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA21334; Fri, 31 Oct 1997 12:13:23 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA25540; Fri, 31 Oct 1997 12:13:20 -0700 (MST) Date: Fri, 31 Oct 1997 12:13:20 -0700 (MST) Message-Id: <199710311913.MAA25540@rocky.mt.sri.com> From: Nate Williams <nate@mt.sri.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey <chuckr@glue.umd.edu> Cc: Simon Shapiro <Shimon@i-connect.net>, John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-current@freebsd.org Subject: Re: More on LINT Kernel Failure to compile In-Reply-To: <Pine.BSF.3.96.971031121427.11985C-100000@picnic.mat.net> References: <XFMail.971031093401.Shimon@i-Connect.Net> <Pine.BSF.3.96.971031121427.11985C-100000@picnic.mat.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid 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. > > I thought that the LINT file was only intended to yield a maximal set of > sources, suitable for linting, and could not compile, because many of the > options chosen for lint would be mutually exclusive. No one would ever, > ever be intended to run a LINT kernel. Close. It's *supposed* to compile (and link) so you can see any errors in the system, but it will never run. Nate