Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Apr 2008 20:36:55 -0500
From:      "Larry Rosenman" <>
To:        "'Conrad J. Sabatier'" <>
Cc:, 'Jeremy Chadwick' <>, 'Kemian Dang' <>
Subject:   RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
Message-ID:  <000001c8a287$07037190$150a54b0$@org>
In-Reply-To: <>
References:  <>	<>	<>	<010b01c8a163$b95133c0$2bf39b40$@org> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Do you have a Current 8-Current?  What is the date of your sources?

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

On Fri, 18 Apr 2008 09:51:36 -0500
"Larry Rosenman" <> 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
-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

Want to link to this message? Use this URL: <$07037190$150a54b0$>