From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 19:11:01 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 8F2A091F; Tue, 12 Mar 2013 19:11:01 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ia0-x231.google.com (mail-ia0-x231.google.com [IPv6:2607:f8b0:4001:c02::231]) by mx1.freebsd.org (Postfix) with ESMTP id 312A8688; Tue, 12 Mar 2013 19:11:01 +0000 (UTC) Received: by mail-ia0-f177.google.com with SMTP id y25so180865iay.36 for ; Tue, 12 Mar 2013 12:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=snufR6p8yF7vbCwSlbGNBgnOa+YhksQGwg0YM27pmZ4=; b=BQtvoOQUogYLPYUKJ1A+Oo44v9+IPr4tyk1EHthT4DI3/NtsCpSMQsoFYCpv2aL2oi zRFP9QFgTaL5xdW5uYmvW1YJ0hWddNTqTjQeip1wpWLz3fvVgn5JEA4US+qIknmmnPlr OrSYLs1xqSHWU4d9qxNnJOmleBKE5x9gZghry5gen7OL9S9FBAd3oTY2ws0R/ErtOYa4 XEKghD+9xjWfeKtJ6vpxerMX9o4ChqzHaInIOjC7ZK+Yqg8Rwx3O4KQTLyPMcLlw+yFG vSDaj8g3xYnW9NswbrE811sm5ioqg2YN285ybmXLwMKkMk2v6N4bI4fQZ1S7LkRzJLcG ibiQ== X-Received: by 10.50.195.134 with SMTP id ie6mr12734330igc.6.1363115460868; Tue, 12 Mar 2013 12:11:00 -0700 (PDT) Received: from oddish.sandvine.com ([64.7.137.182]) by mx.google.com with ESMTPS id ih1sm21170795igc.3.2013.03.12.12.10.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 12:11:00 -0700 (PDT) Sender: Mark Johnston Date: Tue, 12 Mar 2013 15:10:53 -0400 From: Mark Johnston To: Steve Kargl Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130312191053.GB3372@oddish.sandvine.com> 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> <20130311211851.GA12143@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130311211851.GA12143@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dimitry Andric , 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: Tue, 12 Mar 2013 19:11:01 -0000 On Mon, Mar 11, 2013 at 02:18:51PM -0700, Steve Kargl wrote: > 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. Sorry about this, I will revert it and revisit the problem. I've been using bsdgrep by default for a while and somehow haven't run into this. -Mark