From owner-freebsd-bugs@FreeBSD.ORG Sun Apr 14 06:52:36 2013 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 97E2C5F9; Sun, 14 Apr 2013 06:52:36 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 58ABC316; Sun, 14 Apr 2013 06:52:36 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 8A72423F804; Sun, 14 Apr 2013 02:52:33 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us 8A72423F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Sun, 14 Apr 2013 02:52:30 -0400 From: Glen Barber To: "Simon J. Gerraty" Subject: Re: conf/177845: WITH_BMAKE does not work on CURRENT Message-ID: <20130414065230.GC35777@glenbarber.us> References: <201304140420.r3E4K0Et063274@freefall.freebsd.org> <9B5C1BF8-17FB-4718-8AF1-3F8F5E55DAB8@gmail.com> <20130414054224.6720958097@chaos.jnpr.net> <866FF12C-2525-4A59-B20B-39A0522D7B44@gmail.com> <20130414062049.B0C8958097@chaos.jnpr.net> <670AA8F8-B4EA-4D13-B892-EB94BF88F046@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <670AA8F8-B4EA-4D13-B892-EB94BF88F046@gmail.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-bugs@FreeBSD.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 06:52:36 -0000 Simon, On Sat, Apr 13, 2013 at 11:33:53PM -0700, Garrett Cooper wrote: > > [...] > > I've just updated a tree to try to reproduce. > > Are you sure /usr/bin/make is bmake? > > This looks exactly like the same problem I reported to you in private (to make sure I was not doing something incorrectly with '-j' expectation) a few months ago. Glen