From owner-freebsd-stable Mon Oct 2 15:18: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.flashcom.net (3ff83059.dsl.flashcom.net [63.248.48.89]) by hub.freebsd.org (Postfix) with ESMTP id E5EBC37B66D for ; Mon, 2 Oct 2000 15:17:53 -0700 (PDT) Received: (from cgaff@localhost) by mail.flashcom.net (8.11.0/8.11.0) id e92MHOp01024 for freebsd-stable@FreeBSD.ORG; Mon, 2 Oct 2000 17:17:24 -0500 (CDT) (envelope-from cgaff) Date: Mon, 2 Oct 2000 17:17:24 -0500 From: "Corey G." To: freebsd-stable@FreeBSD.ORG Subject: Re: Signal 4 while compiling 4.1.1 Message-ID: <20001002171724.A987@flashcom.net> References: <59131.970508456@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <59131.970508456@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Mon, Oct 02, 2000 at 10:40:56AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried this method yesterday and still received a signal 4. I am anxiously waiting for Jeff Duffy's attempt on a 3rd AMD machine. Thanks, Corey On Mon, Oct 02, 2000 at 10:40:56AM -0700, Jordan Hubbard wrote: > > While I look for cooling issues on the K6-III, I'm still going to try a > > 4.1-STABLE and a 4.1.1-STABLE buildworld on another K6-II 500 machine I > > have, to generate some empirical data on the issue. If both compile > > cleanly, I'll post the info so at least I can kill the thread I > > helped start :) > > Another thing you might try is totally blowing away your source tree > and getting another copy via an authoritative source. In cases where > I'm genuinely not sure myself, I also blow away the host environment > (do a fresh install) and try that. If I still get a compilation > error, I then figure that's a clear smoking gun. This may seem like a > rather onerous set of steps to go through, but the set of > inter-dependencies between the host compilation environment and the > target source tree is so huge that literally anything can happen if > the littlest thing is unsynched. It also helps to have a test box > one can completely blow away, of course.. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---end quoted text--- -- Best Regards, Corey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message