Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed

[Larry Rosenman]

Do you have a Current 8-Current?  What is the date of your sources?



-----Original Message-----
From: Conrad J. Sabatier [mailto:conrads at cox.net] 
Sent: Saturday, April 19, 2008 8:26 PM
To: Larry Rosenman
Cc: 'Kemian Dang'; 'Jeremy Chadwick'; ports at freebsd.org
Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed

On Fri, 18 Apr 2008 09:51:36 -0500
"Larry Rosenman" <ler at lerctr.org> wrote:

> You need to upgrade your system sources.  The way the developers have
> implemented some locking changes makes it hard for the lsof configure
> script to do the right thing. 
> 
> Please upgrade to current RELENG_7, and all should be fine with the
> 4.79,1 port.
> 
> Thanks!
> Larry Rosenman
> sysutils/lsof maintainer.

The lsof upgrade fails in a slightly different manner under 8-CURRENT:

cc  -pipe -Wno-error -fno-strict-aliasing -Wno-error
-DHASEFFNLINK=i_effnlink -D HASF_VNODE -DHASCPUMASK_T -DHASSBSTATE
-DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_ UDEV -DHAS_SI_PRIV
-DHAS_SYS_SX_H -DHAS_LOCKF_ENTRY -DFREEBSDV=8000 -DHASFDESCFS=2
-DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME
-DLSOF_VSTR=\"8.0-CURRENT\ " -I/usr/src/sys -O2 -c dnode.c
dnode.c: In function 'process_node':
dnode.c:760: error: 'struct inode' has no member named 'i_lockf'
dnode.c:761: error: 'struct inode' has no member named 'i_lockf'
*** Error code 1

So...good to go with RELENG_7, but not HEAD?  Hmmm.

-- 
Science is the record of dead religions.
		-- Oscar Wilde