lsof won't build
in [Ports]
|
From: Robert Huff on 19 Sep 2009 19:43 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? 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: "Larry Rosenman" on 20 Sep 2009 00:14 (pardon the top-post, lousy work email client) Also, some of the kernel structures lsof needs aren't exported to /usr/include. The best thing to do when lsof won't build is to make sure you have done a make buildworld & make installworld with the same sources that are in /usr/src, and match the running kernel. Thanks, Larry Rosenman sysutils/lsof maintainer. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler(a)lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -----Original Message----- From: owner-freebsd-ports(a)freebsd.org [mailto:owner-freebsd-ports(a)freebsd.org] On Behalf Of Robert Huff Sent: Saturday, September 19, 2009 6:42 PM To: Lowell Gilbert Cc: freebsd-ports(a)freebsd.org Subject: Re: lsof won't build 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? 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" _______________________________________________ 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 20 Sep 2009 13:45 Robert Huff <roberthuff(a)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. _______________________________________________ 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 20 Sep 2009 15:15 Lowell Gilbert writes: > 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. If you say so. My recent experience started with lsof compiled under stock 8.0 beta 4, which was was incompatible with some change that happened around the branch of 9.0 CURRENT. And there's nothing in {src, ports}/UPDATING which would suggest the need for a change. 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: Erik Trulsson on 20 Sep 2009 16:30
On Sun, Sep 20, 2009 at 03:15:32PM -0400, Robert Huff wrote: > Lowell Gilbert writes: > > > 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. > > If you say so. My recent experience started with lsof compiled > under stock 8.0 beta 4, which was was incompatible with some change > that happened around the branch of 9.0 CURRENT. And there's nothing > in {src, ports}/UPDATING which would suggest the need for a change. But that is not within a major-number release. 8.0 is still not released and from a compatibility view should still be considered as -CURRENT, and 9.0-CURRENT is, well, -CURRENT. In -CURRENT non-compatible changes do happen from time to time, and is often not mentioned in UPDATING, because people running -CURRENT are not supposed to need such reminders. -- <Insert your favourite quote here.> Erik Trulsson ertr1013(a)student.uu.se _______________________________________________ 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" |