From owner-freebsd-ports@FreeBSD.ORG Sat Sep 19 22:16:27 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D4B41065672 for ; Sat, 19 Sep 2009 22:16:27 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.freebsd.org (Postfix) with ESMTP id 17A4E8FC13 for ; Sat, 19 Sep 2009 22:16:27 +0000 (UTC) Received: (qmail 15284 invoked from network); 19 Sep 2009 22:16:26 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 Sep 2009 22:16:26 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 574E65089C; Sat, 19 Sep 2009 18:16:22 -0400 (EDT) From: Lowell Gilbert To: freebsd-ports@freebsd.org References: <19125.7112.336613.902328@jerusalem.litteratus.org> <19125.15684.498698.855972@jerusalem.litteratus.org> Date: Sat, 19 Sep 2009 18:16:22 -0400 In-Reply-To: <19125.15684.498698.855972@jerusalem.litteratus.org> (Robert Huff's message of "Sat, 19 Sep 2009 16:21:24 -0400") Message-ID: <4463bemvgp.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: lsof won't build X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2009 22:16:27 -0000 Robert Huff writes: > Paul Schmehl writes: > >> > The usual casue of this is the installed kernel(+world ??) >> > being out of sync with the contents of /usr/src. >> >> That doesn't make sense to me. vm.h is a src file. > > I have not read the code ... but as I understnd it, the build > process draws on header files from both /usr/include and /usr/src. > If the two disagree - . Not exactly. Buildworld first builds the toolchain from the source tree, then uses that toolchain to build the rest of the system. lsof isn't part of the system build; it comes from the ports system. >> Are you saying you rebuilt kernel and lsof built fine afterwards? Right. lsof needs to look at kernel structures, so it has to be built from the same headers that the kernel was, or it won't know how to interpret the data it retrieves.