From owner-svn-src-all@FreeBSD.ORG Mon Dec 16 13:32:47 2013 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9EE42583; Mon, 16 Dec 2013 13:32:47 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 5E3E71047; Mon, 16 Dec 2013 13:32:47 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id 112137E6A; Mon, 16 Dec 2013 13:32:40 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id E3A191D55; Mon, 16 Dec 2013 14:32:39 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John Baldwin Subject: Re: svn commit: r259010 - in head/sys: conf powerpc/fpu References: <201312052149.rB5LnEcT011811@svn.freebsd.org> <201312051650.26379.jhb@freebsd.org> <86a9g5uofn.fsf@nine.des.no> <201312131231.04749.jhb@freebsd.org> Date: Mon, 16 Dec 2013 14:32:39 +0100 In-Reply-To: <201312131231.04749.jhb@freebsd.org> (John Baldwin's message of "Fri, 13 Dec 2013 12:31:04 -0500") Message-ID: <86k3f4kjk8.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 13:32:47 -0000 John Baldwin writes: > Dag-Erling Sm=C3=B8rgrav writes: > > John Baldwin writes: > > > LINT64 is yet another kernel config covered by 'make tinderbox', > > > but not by the periodic tinderbox. It is probably worth adding to > > > the periodic tinderbox (someday it'd be nice if the two > > > tinderboxes built the same set of things). > > Some day it would be nice if people talked to me directly instead of > > sniping from the sidelines. > Ah, but when people have raised this exact issue before (that tcbuild > and 'make tinderbox' build different things), you have blown them off > repeatedly. I have no idea what tcbuild is. I blow people off when they complain that the tinderbox doesn't work exactly like 'make tinderbox' because it's not intended to. > > Oh, and 'make tinderbox' should die. > No, it is very developer friendly as it Just Works(tm) as a single > command from an existing source tree checkout. We already had 'make universe'. The story behind 'make tinderbox' is that Alfred threw a fit over a tinderbox breakage and insisted, despite being provided with ample proof to the contrary, that my tinderbox was a black box which nobody knew how worked and nobody could reproduce and that tinderbox reports were therefore worthless. He then proceeded to implement 'make tinderbox' purely to piss me off. It serves no other purpose and needs to die. > It also happens to build more of the tree than the periodic tinderbox > (by building more kernel configs, albeit doing quite a bit of > duplicate work for platforms like arm in the process). That's simply not true. The tinderbox builds exactly the same kernels as 'make tinderbox' if they're present. The issue here is that a bug in the source tree prevents some of these kernel configurations from being generated, hence the tinderbox cannot build them. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no