From owner-freebsd-questions@FreeBSD.ORG Tue Jul 28 20:29:52 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9C74106564A for ; Tue, 28 Jul 2009 20:29:52 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 651C68FC0A for ; Tue, 28 Jul 2009 20:29:52 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 18206 invoked from network); 28 Jul 2009 20:29:51 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 28 Jul 2009 20:29:51 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 5DAE65082A; Tue, 28 Jul 2009 16:29:50 -0400 (EDT) To: gula nito References: From: Lowell Gilbert Date: Tue, 28 Jul 2009 16:29:50 -0400 In-Reply-To: (gula nito's message of "Tue\, 28 Jul 2009 15\:08\:57 -0300") Message-ID: <44prbkmtz5.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Failing to compile a new kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2009 20:29:53 -0000 gula nito writes: > Hello, Im trying to compile a new kernel, but when I try to make it , I > receive the following error: > * > ***Error code 1 > > Stop in /usr/obj/usr/src/sys/TEST28JUL09. > ***Error code 1 > > Stop in /usr/src. > ***Error code 1 > > Stop in /usr/src.* The actual error was a little higher up. > The last "MAKE" that appears in the terminal was *"MAKE=make sh > /usr/src/sys/conf/newvers.sh TEST28JUL09"* First of all, you can usually stick with the GENERIC kernel unless you need something particular. If you are going to change it, then the approach you should take is to make a few changes at a time. That way, if the build fails, you can reverse those changes and figure out what was wrong with them. > I adjunt the configuration file Looks like you included NFS_LOCKD without including NFS. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/