From owner-freebsd-ports@FreeBSD.ORG Wed Aug 6 02:28:54 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E286106564A for ; Wed, 6 Aug 2008 02:28:54 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id D56578FC13 for ; Wed, 6 Aug 2008 02:28:53 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 653525CFD; Tue, 5 Aug 2008 22:09:25 -0400 (EDT) X-Virus-Scanned: amavisd-new+ClamAV at codefab.com Received: from [10.152.145.120] (72-165-115-225.dia.static.qwest.net [72.165.115.225]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTPSA id 0733A5CCB; Tue, 5 Aug 2008 22:09:22 -0400 (EDT) Message-Id: From: Chuck Swiger To: Stuart Barkley In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) Date: Tue, 5 Aug 2008 19:09:18 -0700 References: <56E45E0F-29D4-4CA8-9936-384405AB874A@mac.com> <4897518D.4090001@FreeBSD.org> <20080804201806.GA50143@nagual.pp.ru> X-Mailer: Apple Mail (2.928.1) Cc: freebsd-ports@freebsd.org Subject: Re: bsd-grep-20080725_1 -v flag busted... 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: Wed, 06 Aug 2008 02:28:54 -0000 On Aug 5, 2008, at 5:10 PM, Stuart Barkley wrote: [ ... ] > Yes, I was seeing problems building several ports with the latest > bsdgrep port. Specifically the neon28 and avifile ports where hanging > in the ./configure phase as shown at in the original message in this > thread. Thanks for the confirmation, Stuart, as well as your analysis of what the configure script was trying to do with grep that was resulting in the endless loop. Regards, -- -Chuck