From owner-freebsd-stable@FreeBSD.ORG Fri Aug 8 20:34:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E2F91065673 for ; Fri, 8 Aug 2008 20:34:02 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 17CC08FC17 for ; Fri, 8 Aug 2008 20:34:01 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m78KXwpP037001; Fri, 8 Aug 2008 16:33:59 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m78KXw7G009888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Aug 2008 16:33:58 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200808082033.m78KXw7G009888@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 08 Aug 2008 16:34:01 -0400 To: "Kevin Oberman" , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20080808200447.8F9954501A@ptavv.es.net> References: <20080808200447.8F9954501A@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: Unable to build kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2008 20:34:02 -0000 At 04:04 PM 8/8/2008, Kevin Oberman wrote: >Today I was unable to build a new kernel for 7-Stable. It dies when >linking the kernel, seemingly because of not finding the definitions for >some nfs stuff. I don't use nfs and always exclude both server and >client from my kernel. (Long config attached, if the list does not strip >nooptions NFSCLIENT # Network Filesystem Client >nooptions NFSSERVER # Network Filesystem Server >nooptions NFS_ROOT # NFS usable as root device, requires Can you build generic on its own ? What if you add to your config nooptions NFSLOCKD which recently got added to GENERIC. ---Mike