From owner-freebsd-ports@FreeBSD.ORG Sun Oct 16 21:06:53 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1087C16A41F for ; Sun, 16 Oct 2005 21:06:53 +0000 (GMT) (envelope-from krinklyfig@comcast.net) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.76.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D5F243D49 for ; Sun, 16 Oct 2005 21:06:52 +0000 (GMT) (envelope-from krinklyfig@comcast.net) Received: from smogmonster.local (pcp0010916331pcs.albqrq01.nm.comcast.net[68.35.114.183]) by comcast.net (sccrmhc14) with ESMTP id <2005101621065101400n5s6ke>; Sun, 16 Oct 2005 21:06:51 +0000 From: Joshua Tinnin To: freebsd-ports@freebsd.org Date: Sun, 16 Oct 2005 15:06:37 -0600 User-Agent: KMail/1.8.2 References: <200510161104.27533.krinklyfig@comcast.net> <20051016195150.GB90311@xor.obsecurity.org> In-Reply-To: <20051016195150.GB90311@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510161506.40003.krinklyfig@comcast.net> Cc: Kris Kennaway Subject: Re: lsof-4.76 build fails X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2005 21:06:53 -0000 On Sun 16 Oct 05 13:51, Kris Kennaway wrote: > On Sun, Oct 16, 2005 at 11:04:24AM -0600, Joshua Tinnin wrote: > > I notice the last commit says in the log: "This time really fix the > > build on RELENG_6" (the previous one said, "Update to snapshot > > version to fix 6.0 build problems"). Well, I am still on BETA5, but > > lsof built fine up until the latest commit, though I didn't try to > > build after Saturday's commit. > > Update to the subsequent commit. I have. My ports tree is updated every day at 6am (MDT), and I tried upgrading the port after that today. Just to be sure, I supped again just a few minutes ago and am getting the same error. The upgrade is from 4.76 to 4.76.1.1. - jt