Date: Sat, 19 Sep 2009 18:16:22 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: freebsd-ports@freebsd.org Subject: Re: lsof won't build Message-ID: <4463bemvgp.fsf@be-well.ilk.org> In-Reply-To: <19125.15684.498698.855972@jerusalem.litteratus.org> (Robert Huff's message of "Sat, 19 Sep 2009 16:21:24 -0400") References: <AFAFEC417BA4553D76CE1E64@Macintosh-2.local> <19125.7112.336613.902328@jerusalem.litteratus.org> <F32849953E3C729353C762ED@Macintosh-2.local> <19125.15684.498698.855972@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Huff <roberthuff@rcn.com> 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 - <throat-slitting motion>. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4463bemvgp.fsf>