Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Apr 2008 16:05:04 +0100
From:      "Kemian Dang" <dangkm@gmail.com>
To:        "Larry Rosenman" <ler@lerctr.org>
Cc:        ports@freebsd.org, Jeremy Chadwick <koitsu@freebsd.org>
Subject:   Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
Message-ID:  <82f916c90804180805x1035c8delcc41c5834f92d015@mail.gmail.com>
In-Reply-To: <010b01c8a163$b95133c0$2bf39b40$@org>
References:  <82f916c90804180434l2f87842ar6398ec09d3e45c3c@mail.gmail.com> <20080418124557.GA40620@eos.sc1.parodius.com> <82f916c90804180706k3717ccf3u97b5c401a735d58c@mail.gmail.com> <010b01c8a163$b95133c0$2bf39b40$@org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Larry,

Thanks for the information, I will upgrade the system when I have time.

Best wishes,
Kemian

On 18/04/2008, Larry Rosenman <ler@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.
>
>
>  --
>  Larry Rosenman                     http://www.lerctr.org/~ler
>  Phone: +1 512-248-2683                E-Mail: ler@lerctr.org
>  US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
>
>
>
>  -----Original Message-----
>  From: owner-freebsd-ports@freebsd.org
>  [mailto:owner-freebsd-ports@freebsd.org] On Behalf Of Kemian Dang
>  Sent: Friday, April 18, 2008 9:06 AM
>  To: Jeremy Chadwick
>  Cc: ports@freebsd.org
>  Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
>
>  Hi, Jeremy,
>
>  Thank you for information, it's my fault ignoring the list information.
>
>  After checking mails, the maintainer said this problem would be fixed
>  at 4.79L and my upgrading is from 4.79K to 4.79,1.
>  If version 4.79,1 is higher than 4.79L, I think this should be fixed
>  already.
>
>  Or should I upgrade the whole system?
>
>  I use i386 version of FreeBSD 7 Stable on a amd 64 platform. It was
>  built on Mar 17 2008.
>
>  Best wishes,
>  Kemian
>
>  On 18/04/2008, Jeremy Chadwick <koitsu@freebsd.org> wrote:
>  > On Fri, Apr 18, 2008 at 12:34:37PM +0100, Kemian Dang wrote:
>  >  > Hi,
>  >  >
>  >  > I cvsup the port just now and upgrade port using "portupgrade -a", get
>  >  > an error on lsof, the error point of the output is:
>  >  >
>  >  > cc  -fno-strict-aliasing -pipe -DHASEFFNLINK=i_effnlink -DHASF_VNODE
>  >  > -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2
>  >  > -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DHAS_ZFS
>  >  > -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6
>  >  > -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-STABLE\" -I/usr/src/sys -O2 -c
>  >  > dnode.c
>  >  > dnode.c: In function 'get_lock_state':
>  >  > dnode.c:113: error: 'struct lockf' has no member named 'lf_flags'
>  >  > dnode.c:115: error: 'struct lockf' has no member named 'lf_id'
>  >  > dnode.c:121: error: 'struct lockf' has no member named 'lf_id'
>  >  > dnode.c:129: error: 'struct lockf' has no member named 'lf_start'
>  >  > dnode.c:130: error: 'struct lockf' has no member named 'lf_end'
>  >  > dnode.c:134: error: 'struct lockf' has no member named 'lf_type'
>  >  > dnode.c:136: error: 'struct lockf' has no member named 'lf_type'
>  >  > dnode.c:138: error: 'struct lockf' has no member named 'lf_type'
>  >  > dnode.c:141: error: 'struct lockf' has no member named 'lf_next'
>  >  > *** Error code 1
>  >  >
>  >  > Stop in /usr/ports/sysutils/lsof/work/lsof_4.79/lsof_4.79_src.
>  >  >
>  >  > Does anyone else has such error, or it is my problem.
>  >
>  >
>  > Did you check the mailing list at all?  Others have reported this
>  >  problem with version 4.79K:
>  >
>  >  http://lists.freebsd.org/pipermail/freebsd-ports/2008-April/048020.html
>  >
>  >  FYI, I have absolutely no problem building the latest lsof port (4.79)
>  >  on RELENG_7 amd64.  Here's the result of my compile:
>  >
>  >  cc  -fno-strict-aliasing -pipe -march=nocona -march=nocona
>  -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T -DHASSBSTATE
>  -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H
>  -DHAS_ZFS -DHAS_LOCKF_ENTRY -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS
>  -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-STABLE\"
>  -I/usr/src/sys -O2 -c dnode.c
>  >  cc  -fno-strict-aliasing -pipe -march=nocona -march=nocona
>  -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T -DHASSBSTATE
>  -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H
>  -DHAS_ZFS -DHAS_LOCKF_ENTRY -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS
>  -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-STABLE\"
>  -I/usr/src/sys -O2 -c dnode1.c
>  >  cc -fno-strict-aliasing -pipe -march=nocona -march=nocona -DFREEBSDV=7000
>  -DHAS_ZFS -D_SOLARIS_C_SOURCE -O2 -I/usr/src/sys/compat/opensolaris
>  -I/usr/src/sys/contrib/opensolaris/uts/common/fs/zfs
>  -I/usr/src/sys/contrib/opensolaris/uts/common/zmod
>  -I/usr/src/sys/contrib/opensolaris/uts/common -Iusr/src/sys
>  -I/usr/src/sys/contrib/opensolaris/common/zfs
>  -I/usr/src/sys/contrib/opensolaris/common
>  -I/usr/ports/sysutils/lsof/work/lsof_4.79/lsof_4.79_src/usr/src/include
>  -I`pwd` -c dnode2.c
>  >
>  >  ...and so on.  Works fine.
>  >
>  >
>  >  --
>  >  | Jeremy Chadwick                                    jdc at parodius.com
>  |
>  >  | Parodius Networking                           http://www.parodius.com/
>  |
>  >  | UNIX Systems Administrator                      Mountain View, CA, USA
>  |
>  >  | Making life hard for others since 1977.                  PGP: 4BD6C0CB
>  |
>  >
>  >
>
> _______________________________________________
>  freebsd-ports@freebsd.org mailing list
>  http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>  To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82f916c90804180805x1035c8delcc41c5834f92d015>