From owner-freebsd-current@FreeBSD.ORG Tue Sep 21 01:53:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF84116A4CE for ; Tue, 21 Sep 2004 01:53:49 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4010643D1D for ; Tue, 21 Sep 2004 01:53:49 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i8L1rlOO013515; Mon, 20 Sep 2004 21:53:48 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <414F6115.8050201@savvis.net> References: <414F4507.2010609@savvis.net> <414F6115.8050201@savvis.net> Date: Mon, 20 Sep 2004 21:53:47 -0400 To: Maksim Yevmenkin From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: sparc64 buildworld is broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2004 01:53:50 -0000 At 4:00 PM -0700 9/20/04, Maksim Yevmenkin wrote: >Hello, Hi. >Garance A Drosihn wrote: >> >>I have only glanced at this, but here's my standard question: >>What release are you trying to build? You are starting at a >>5.2.1-release system, but what are you updating to? > >err, sorry... for some reason i thought it was clear :) yes, i'm >trying to build 6-current cvsup'ed few hours ago. > >>The little that I can add is that I just finished a buildworld on >>sparc64 last night, [...] I was building a 6.x-current system, but >>there would be several extra steps that you really must do if you >>are upgrading from 5.2.1-release to 5.x-latest or 6.x-current... > >ok, what exactly is required? i quickly glanced at UPDATING and >UPDATING.64BTT and did not find anything related. perhaps I >missed it? You should not "glance through" UPDATING.64BTT, unless you have already made the transition from 32-bit time_t to 64-bit time_t. You have to do one buildworld with a 32-bit time_t, install that, and then do a second build with the exact same sources except for changing time_t. I must admit I haven't looked at this since I finished the writeup and the commits to switch the tree to 64-bit time_t. I started to look in July, but was sidetracked by some other problems. It may be prudent to first update to just before we made the transition, then make the transition, and then update to -current. That would mean three buildworlds. Depending on your situation, it might make more sense to just reinstall from the latest ISO for 5.3-beta, and thus avoid any issues with the 64bTT transition. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu