From owner-freebsd-current@FreeBSD.ORG Thu May 19 20:55:46 2005 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 CC29B16A4CE; Thu, 19 May 2005 20:55:46 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0115143D53; Thu, 19 May 2005 20:55:42 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j4JKwrYp096199; Thu, 19 May 2005 14:58:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <428CFD0F.4030800@samsco.org> Date: Thu, 19 May 2005 14:54:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Gurvich References: <20050518051111.GA33262@Athena.infor.org> <20050518223616.3f515599@dolphin.local.net> <20050519112345.pkuuiedxwswkkk40@netchild.homeip.net> <200505191521.46254.david.freebsd@verizon.net> In-Reply-To: <200505191521.46254.david.freebsd@verizon.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: Newest loader from CVS not working 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: Thu, 19 May 2005 20:55:46 -0000 David Gurvich wrote: > Yes that can be done. The problem can be worked around. Should not need to > be. I can use the loader from 5.3-RELEASE iso, but cannot use any from > cvsup. The point here is how to fix the problem so that when building the > loader works. > Yes, something has changed that is causing problems. Would you be willing to rewind your source tree incrementally until you find the point where the loader works again? Once we know where that point is, it'll be a whole lot easier to fix it. I'm going to consider this a show-stopper on 6-current until it gets fully investigated. Scott