From owner-freebsd-ports@FreeBSD.ORG Sun Sep 20 17:45:10 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 87EEF106566B for ; Sun, 20 Sep 2009 17:45:10 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5E1058FC19 for ; Sun, 20 Sep 2009 17:45:10 +0000 (UTC) Received: (qmail 5813 invoked from network); 20 Sep 2009 17:45:09 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Sep 2009 17:45:09 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id E376E508A8; Sun, 20 Sep 2009 13:45:02 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 452A31CC4F; Sun, 20 Sep 2009 13:45:02 -0400 (EDT) From: Lowell Gilbert To: Robert Huff References: <19125.7112.336613.902328@jerusalem.litteratus.org> <19125.15684.498698.855972@jerusalem.litteratus.org> <4463bemvgp.fsf@be-well.ilk.org> <19125.27730.939946.690659@jerusalem.litteratus.org> Date: Sun, 20 Sep 2009 13:45:01 -0400 In-Reply-To: <19125.27730.939946.690659@jerusalem.litteratus.org> (Robert Huff's message of "Sat, 19 Sep 2009 19:42:10 -0400") Message-ID: <448wg9o6hu.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-ports@freebsd.org 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: Sun, 20 Sep 2009 17:45:10 -0000 Robert Huff writes: > Lowell Gilbert writes: > >> >> 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. > > And it finds those not in /usr/include - which, as I understand > things, will in a correctly configured system definitionally match > what's in the running kernel - but in /usr/src, for which such an > expectation is wobbly? It seems to me (fairly short investigation) that it uses kernel structures that aren't in /usr/include. That means it must be looking in /usr/src/sys. If those sources don't match the installed kernel exactly, that typically won't be a problem, because kernel interfaces are intended to not change within a major-number release.