From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 21:18:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4AF5F625; Mon, 11 Mar 2013 21:18:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 0DDAE250; Mon, 11 Mar 2013 21:18:58 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r2BLIqPm012203; Mon, 11 Mar 2013 14:18:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r2BLIpkm012202; Mon, 11 Mar 2013 14:18:51 -0700 (PDT) (envelope-from sgk) Date: Mon, 11 Mar 2013 14:18:51 -0700 From: Steve Kargl To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130311211851.GA12143@troutmask.apl.washington.edu> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> <1UF7wX-000BVL-0y@internal.tormail.org> <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , =?iso-8859-1?Q?G=E1bor_K=F6vesd=E1n?= , freebsd-ports@freebsd.org, Niclas Zeising , "O. Hartmann" , Mark Johnston , Jan Beich X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 21:18:58 -0000 On Mon, Mar 11, 2013 at 10:05:47PM +0100, Dimitry Andric wrote: > On 2013-03-11 20:00, Jan Beich wrote: > > Dimitry Andric writes: > > > >> $ echo 'sub/foo.barx' | grep sub/foo.bar > >> $ echo $? > >> 1 > > > > $ echo 'sub/foo.barx' | env -i grep sub/foo.bar > > $ echo 'sub/foolbarx' | env -i grep sub/foo.bar > > $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' > > sub/foo.barx > > $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar > > sub/foo.bar > > $ echo 'sub/foo.barx' | env -i grep --color=no sub/foo.bar > > sub/foo.barx > > > > A buggy shortcut? > > No, after some digging in and debugging of the bsdgrep code, I > found out it is a regression caused by r246917, which is a fix > for "bin/175213: [patch] bsdgrep(1) segfaults upon malicious input". > If you revert it, bsdgrep starts working correctly again. First, I can report that bootstrapping gcc-4.8.0 works if I use gnugrep instead of bsdgrep. The above explains why I had previously seen the failure as I was using an older bsdgrep. Second, an apology is owed to the clang gang as I attributed the problem to clang as it showed up on my system after converted everything over to clang. > I think it would be best to back out r246917 for now, until the > regression can be fixed properly. Having bsdgrep crash is bad, > but not returning any results while it should is even worse... I tend to agree with your assessment that r246817 should be reverted, because I hit this issue in configure scripts and there is a large amount of software that uses autotool for configuration. -- Steve