From owner-freebsd-current@FreeBSD.ORG Wed Jun 18 23:06:34 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A33E1065673; Wed, 18 Jun 2008 23:06:34 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.freebsd.org (Postfix) with ESMTP id 654278FC1D; Wed, 18 Jun 2008 23:06:34 +0000 (UTC) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id AF54D73319; Wed, 18 Jun 2008 23:06:33 +0000 (GMT) Date: Wed, 18 Jun 2008 23:06:33 +0000 From: John Birrell To: "Bjoern A. Zeeb" Message-ID: <20080618230633.GB20863@what-creek.com> References: <20080618085948.X83875@maildrop.int.zabbadoz.net> <20080618224531.GA20863@what-creek.com> <20080618225126.V83875@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080618225126.V83875@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.4.2.3i Cc: John Birrell , FreeBSD current mailing list Subject: Re: problem: world boot strapping from 7-C to HEAD with CDDL on sparc64? 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: Wed, 18 Jun 2008 23:06:34 -0000 On Wed, Jun 18, 2008 at 10:53:02PM +0000, Bjoern A. Zeeb wrote: > On Wed, 18 Jun 2008, John Birrell wrote: > > >On Wed, Jun 18, 2008 at 09:06:41AM +0000, Bjoern A. Zeeb wrote: > >>Hi, > >> > >>I am having a bootstrapping problem on sparc64 with CDDL but cannot > >>find anything in UPDATING for that. > >> > >>See: > >>http://sources.zabbadoz.net/freebsd/tmp/sparc64-compile-world.txt > >> > >>Should that be documented? > > > >Is this an up-to-date RELENG_7 system? If so, I think it should have the > > check the text file references. It has an uname -a in the first line. > > It is a 7-CURRENT from 2006. UPDATING says we support updating from 6 > or newer so something is wrong. Either bootstrapping or UPDATING. I > guess it's the former... I thought our policy was that you had to update to the latest on a RELENG_X branch before updating to the next branch or to current. -- John Birrell