From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 3 09:52:00 2003 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CF7637B401; Thu, 3 Jul 2003 09:52:00 -0700 (PDT) Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D93A4400B; Thu, 3 Jul 2003 09:51:59 -0700 (PDT) (envelope-from welchsm@earthlink.net) Received: from huey.psp.pas.earthlink.net ([207.217.78.220]) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19Y7JP-0007Ca-00; Thu, 03 Jul 2003 09:51:59 -0700 Received: from [207.217.78.205] by EarthlinkWAM via HTTP; Thu Jul 03 09:51:59 PDT 2003 Message-ID: <2054641.1057251119151.JavaMail.nobody@huey.psp.pas.earthlink.net> Date: Thu, 3 Jul 2003 09:49:53 -0500 (GMT) From: Sean Welch To: Peter Grehan Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Web Access Mail version 3.0 cc: freebsd-ppc@freebsd.org Subject: Re: Attempting to cross-compile newest -CURRENT X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2003 16:52:00 -0000 Okay. I've made those changes in my make line... The compiled loader has a problem? I'll use the one from your website, then. Unfortunately I can't send in a debug trace because it isn't a recurring problem. I'm dealing with the results of trying to fix the last kernel panic... Maybe I should go ahead and wipe it out and reinstall using 5.1-RELEASE. Then I can update right away... Bummer. Sean -------Original Message------- From: Peter Grehan Sent: 07/02/03 09:13 PM To: Sean_Welch@alum.wofford.org Subject: Re: Attempting to cross-compile newest -CURRENT > > Hi Sean, > By the way, I added -DNO_WERROR to the list on O'Brien's > suggestion. As I mentioned, that shouldn't be necessary, and might only hide some errors. > I removed the -DNOFORTH option; should I also > remove the -DNO_FORTH option? If not, what is the difference? The loader won't work due to a memory alloc error - still to be debugged. The -DNO_FORTH was a type - it should have been -DNOFORTH. > I did run into another rather strange problem yesterday > and I'm not sure what to do about it. I'm going to have > to post a message to the current mailing list about it > I think. ... > Any suggestions before I mail the current list? Get a backtrace from the debugger (db> t) and post that with the bug report. You might want to disable background fsck in the meantime in your /etc/rc.conf later, Peter. >