From owner-freebsd-current@FreeBSD.ORG Sat Jul 25 12:11:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB82E106566B; Sat, 25 Jul 2009 12:11:06 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6DF818FC0A; Sat, 25 Jul 2009 12:11:06 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:f0d8:4d61:8883:bb3f] (unknown [IPv6:2001:7b8:3a7:0:f0d8:4d61:8883:bb3f]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 7BA6B5C59; Sat, 25 Jul 2009 14:11:05 +0200 (CEST) Message-ID: <4A6AF659.3000709@andric.com> Date: Sat, 25 Jul 2009 14:11:05 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.2pre) Gecko/20090724 Shredder/3.0b4pre MIME-Version: 1.0 To: Mel Flynn References: <20090725054941.GB21885@elvis.mu.org> <200907242300.44148.mel.flynn+fbsd.current@mailing.thruhere.net> In-Reply-To: <200907242300.44148.mel.flynn+fbsd.current@mailing.thruhere.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Alfred Perlstein Subject: Re: weird world break in mklocale X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 25 Jul 2009 12:11:06 -0000 On 2009-07-25 09:00, Mel Flynn wrote: > On Friday 24 July 2009 21:49:41 Alfred Perlstein wrote: >> Anyone see a build break in mklocale? > The archives: > http://lists.freebsd.org/pipermail/freebsd-current/2009-July/thread.html#9406 I guess there is a need to put mklocale into the build bootstrap tools, since IMHO it's a bit of a kludge to have to manually rebuild it before a buildworld can succeed... This will bite everyone who updates from something oldish to -CURRENT now, right?