Date: Sun, 20 Sep 2009 13:45:01 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Robert Huff <roberthuff@rcn.com> Cc: freebsd-ports@freebsd.org Subject: Re: lsof won't build Message-ID: <448wg9o6hu.fsf@lowell-desk.lan> In-Reply-To: <19125.27730.939946.690659@jerusalem.litteratus.org> (Robert Huff's message of "Sat, 19 Sep 2009 19:42:10 -0400") References: <AFAFEC417BA4553D76CE1E64@Macintosh-2.local> <19125.7112.336613.902328@jerusalem.litteratus.org> <F32849953E3C729353C762ED@Macintosh-2.local> <19125.15684.498698.855972@jerusalem.litteratus.org> <4463bemvgp.fsf@be-well.ilk.org> <19125.27730.939946.690659@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Huff <roberthuff@rcn.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448wg9o6hu.fsf>