From: Robert Huff on 19 Sep 2009 14:00 Paul Schmehl writes: > I'm getting this error when trying to install sysutils/lsof: > > /usr/src/sys/vm/vm.h:64:24: error: machine/vm.h: No such file or directory > > Shouldn't machine be some sort of macro that points at the ARCH > of the system lsof is being installed on? Having experienced this recently: The usual casue of this is the installed kernel(+world ??) being out of sync with the contents of /usr/src. The solution is to rebuild/reinstall kernel(+world ??). Perosnally I think it's bad programming also ... but then I'm not the one writing the code. Robert Huff _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Paul Schmehl on 19 Sep 2009 14:17 --On September 19, 2009 1:58:32 PM -0400 Robert Huff <roberthuff(a)rcn.com> wrote: > > Paul Schmehl writes: > >> I'm getting this error when trying to install sysutils/lsof: >> >> /usr/src/sys/vm/vm.h:64:24: error: machine/vm.h: No such file or >> directory >> >> Shouldn't machine be some sort of macro that points at the ARCH >> of the system lsof is being installed on? > > Having experienced this recently: > The usual casue of this is the installed kernel(+world ??) > being out of sync with the contents of /usr/src. > The solution is to rebuild/reinstall kernel(+world ??). > Perosnally I think it's bad programming also ... but then I'm > not the one writing the code. > That doesn't make sense to me. vm.h is a src file. My src files are updated daily. Even if I rebuilt the kernel (this one has been recompiled twelve times already), the src files wouldn't change. The build error is complaining about not being able to find the header file for (I'm assuming) my architecture, not for some binary compiled during the kernel build. Are you saying you rebuilt kernel and lsof built fine afterwards? 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 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Robert Huff on 19 Sep 2009 16:23 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>. > Are you saying you rebuilt kernel and lsof built fine afterwards? Correct. Robert Huff _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Lowell Gilbert on 19 Sep 2009 18:16 Robert Huff <roberthuff(a)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. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Paul Schmehl on 19 Sep 2009 18:29
--On September 19, 2009 6:16:22 PM -0400 Lowell Gilbert <freebsd-ports-local(a)be-well.ilk.org> wrote: > Robert Huff <roberthuff(a)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 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |