From owner-freebsd-ports@FreeBSD.ORG Sat Sep 19 22:28:45 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 E6DBB1065694 for ; Sat, 19 Sep 2009 22:28:45 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.120]) by mx1.freebsd.org (Postfix) with ESMTP id AEACC8FC1C for ; Sat, 19 Sep 2009 22:28:45 +0000 (UTC) Received: from [192.168.2.102] (really [76.182.207.163]) by cdptpa-omta01.mail.rr.com with ESMTP id <20090919222844377.CFJE6569@cdptpa-omta01.mail.rr.com> for ; Sat, 19 Sep 2009 22:28:44 +0000 Date: Sat, 19 Sep 2009 17:28:43 -0500 From: Paul Schmehl To: freebsd-ports@freebsd.org Message-ID: In-Reply-To: <4463bemvgp.fsf@be-well.ilk.org> References: <19125.7112.336613.902328@jerusalem.litteratus.org> <19125.15684.498698.855972@jerusalem.litteratus.org> <4463bemvgp.fsf@be-well.ilk.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: lsof won't build X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl 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:28:46 -0000 --On September 19, 2009 6:16:22 PM -0400 Lowell Gilbert wrote: > 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. Thanks, Lowell. That makes sense. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ****************************************** WARNING: Check the headers before replying