From owner-freebsd-stable Tue Dec 19 17:15: 5 2000 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 19 17:15:04 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.andy.de (fw.andy.de [212.8.198.74]) by hub.freebsd.org (Postfix) with ESMTP id B63AD37B402 for ; Tue, 19 Dec 2000 17:15:03 -0800 (PST) Received: from windoze.andy.de (windoze.andy.de [212.8.199.4]) by mail.andy.de (Postfix) with ESMTP id 630D87CEC2 for ; Wed, 20 Dec 2000 02:14:55 +0100 (CET) Date: Wed, 20 Dec 2000 02:15:24 +0100 From: Andreas Gerstenberg To: STABLE Subject: Re: problems w/ make world... Message-ID: <2320948525.977278524@windoze.andy.de> In-Reply-To: <3A3FFB56.F93F371A@mediaone.net> X-Mailer: Mulberry/2.0.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Eric M Logan wrote: > I'm currently using FreeBSD 4.2 and I cvsup'ed the latest sources > this morning. Everytime I try doing a make buildworld && make > installworld (in single user mode and regular), the whole thing crashes > out w/ signal 11 errors. Any ideas why this might be? And before > anyone suggests hardware problems let me say this. I've been able to > make world many times before w/o and w/ problems. Sometimes I can make > world w/o any errors what so ever. Other times, I have to try making > the world several times until it completes successfully. I've also > tried swapping out ram, drives, nics, motherboards and even CPUs so I > really don't think it's that. Having said that, if anyone could suggest I've had the same problem with the 4.2-RELEASE (new installation) and I've also changed the whole hardware without success. In every try it was the same file (something while compiling gcc) where I got the SIG 11. Since I've installed a 4.1.1-RELEASE and did a cvsup to stable, everything works smoothly.. regards, Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message