Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
do I just need to update my sources and build a kernel or do I need to buildworld? I hope it is just a build kernel because I get stuck on merge master after build world, I don't understand the questions it asks Thank you for your help Sam Fourman Jr. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
On Sat, 19 Apr 2008 21:06:40 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Please do let me know. Still no good. Same exact error with a CURRENT built just this morning (Mon, Apr. 21, 7:00 am CDT). I noticed some conditional compilation stuff in one of the files, based on the version of FreeBSD being used. Perhaps we need some more of that? Thanks! -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:46 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 20:36:55 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Do you have a Current 8-Current? What is the date of your sources? It's a pretty current Current. :-) FreeBSD serene.no-ip.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Apr 18 01:11:50 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM amd64 In the process now of upgrading sources again and rebuilding world/kernel. We'll see what happens. The version of lsof I have in ports is 4.79, the final release version (minus any of the versioning suffix letters). -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] 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. -- Every man thinks God is on his side. The rich and powerful know he is. -- Jean Anouilh, French dramatist and playwright ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
I've sent a note to Vic Abell (lsof author) about this. Thanks for the report. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 7:09 AM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 21:06:40 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Please do let me know. Still no good. Same exact error with a CURRENT built just this morning (Mon, Apr. 21, 7:00 am CDT). I noticed some conditional compilation stuff in one of the files, based on the version of FreeBSD being used. Perhaps we need some more of that? Thanks! -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:46 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 20:36:55 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Do you have a Current 8-Current? What is the date of your sources? It's a pretty current Current. :-) FreeBSD serene.no-ip.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Apr 18 01:11:50 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM amd64 In the process now of upgrading sources again and rebuilding world/kernel. We'll see what happens. The version of lsof I have in ports is 4.79, the final release version (minus any of the versioning suffix letters). -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] 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. -- Every man thinks God is on his side. The rich and powerful know he is. -- Jean Anouilh, French dramatist and playwright ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
On Fri, 18 Apr 2008 14:34:19 -0500 Larry Rosenman wrote: would you mind writing something? I agree, but I'm swamped at $DAYJOB. Thanks for the idea. Sorry, but I can't. I do not understand those details. And my suggestion to write a note to UPDATING base on the fact that you may get those questions from many lsof users which use FreeBSD 7.0. 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. That seems to be a good candidate to /usr/ports/UPDATING. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
It compiles and works well after the upgrading of the system to latest. Thanks. Best wishes, Kemian On 18/04/2008, Kemian Dang [EMAIL PROTECTED] wrote: Hi, Larry, Thanks for the information, I will upgrade the system when I have time. Best wishes, Kemian On 18/04/2008, Larry Rosenman [EMAIL PROTECTED] 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-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kemian Dang Sent: Friday, April 18, 2008 9:06 AM To: Jeremy Chadwick Cc: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 Chadwickjdc at parodius.com | | Parodius Networking
RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
Do you have a Current 8-Current? What is the date of your sources? -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] 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 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
On Sat, 19 Apr 2008 20:36:55 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Do you have a Current 8-Current? What is the date of your sources? It's a pretty current Current. :-) FreeBSD serene.no-ip.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Apr 18 01:11:50 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM amd64 In the process now of upgrading sources again and rebuilding world/kernel. We'll see what happens. The version of lsof I have in ports is 4.79, the final release version (minus any of the versioning suffix letters). -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] 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. -- Man will never be free until the last king is strangled with the entrails of the last priest. -- Denis Diderot, French encyclopedist ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] 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 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
Please do let me know. -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:46 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 20:36:55 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Do you have a Current 8-Current? What is the date of your sources? It's a pretty current Current. :-) FreeBSD serene.no-ip.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Apr 18 01:11:50 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM amd64 In the process now of upgrading sources again and rebuilding world/kernel. We'll see what happens. The version of lsof I have in ports is 4.79, the final release version (minus any of the versioning suffix letters). -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] 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. -- Man will never be free until the last king is strangled with the entrails of the last priest. -- Denis Diderot, French encyclopedist ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
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. Best wishes, Kemian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
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 Chadwickjdc 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 [EMAIL PROTECTED]
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 [EMAIL PROTECTED] 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 Chadwickjdc 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 [EMAIL PROTECTED]
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
Hi, Larry, Thanks for the information, I will upgrade the system when I have time. Best wishes, Kemian On 18/04/2008, Larry Rosenman [EMAIL PROTECTED] 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-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kemian Dang Sent: Friday, April 18, 2008 9:06 AM To: Jeremy Chadwick Cc: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 Chadwickjdc 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 [EMAIL
RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
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-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kemian Dang Sent: Friday, April 18, 2008 9:06 AM To: Jeremy Chadwick Cc: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 Chadwickjdc 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 [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
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. That seems to be a good candidate to /usr/ports/UPDATING. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
would you mind writing something? I agree, but I'm swamped at $DAYJOB. Thanks for the idea. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: Boris Samorodov [mailto:[EMAIL PROTECTED] Sent: Friday, April 18, 2008 1:57 PM To: Larry Rosenman Cc: [EMAIL PROTECTED] 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. That seems to be a good candidate to /usr/ports/UPDATING. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
