Date: Sat, 19 Sep 2009 17:28:43 -0500 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: freebsd-ports@freebsd.org Subject: Re: lsof won't build Message-ID: <B954D5E64B9E0BCFBD09A9A9@Macintosh-2.local> In-Reply-To: <4463bemvgp.fsf@be-well.ilk.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--On September 19, 2009 6:16:22 PM -0400 Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> wrote: > 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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B954D5E64B9E0BCFBD09A9A9>