From owner-freebsd-stable Fri Jan 5 10:17:38 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 10:17:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay3.inwind.it (relay3.inwind.it [212.141.53.74]) by hub.freebsd.org (Postfix) with ESMTP id 0A52037B404 for ; Fri, 5 Jan 2001 10:17:30 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.154.81) by relay3.inwind.it (5.1.056) id 3A40BF860032134E; Fri, 5 Jan 2001 19:09:47 +0100 From: Salvo Bartolotta Date: Fri, 05 Jan 2001 18:11:55 GMT Message-ID: <20010105.18115500@bartequi.ottodomain.org> Subject: Re: 4.2-STABLE build fails To: Keith Jones Cc: Janko van Roosmalen , Odhiambo Washington , FBSD-STABLE In-Reply-To: <20010105151843.A6570@moose.bri.hp.com> References: <20010104095534.A51777@poeza.iconnect.co.ke> <20010105151843.A6570@moose.bri.hp.com> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/5/01, 4:18:43 PM, Keith Jones wrote=20 regarding Re: 4.2-STABLE build fails: > On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > > I've seen much of this discussed here but mine seems to break at t= his > > > point: > > > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > > > ..and with this msg on the console... > > > > > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited= on > > > signal 11 (core dumped) > > > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited= on > > > signal 11 (core dumped) > > > > > > > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not= =20 help. > > > Any pointer what this 13.viref thing is and how I can sort that ou= t=20 will > > > be highly appreciated. > > > > The FreeBSD faq mentions that signal 11 points to hardware problems.= > Could people please STOP spreading this myth that all Signal 11's=20 during > 'make world' are a result of hardware problems. It is highly=20 misleading.=20 Dear FreeBSD'ers, I have seen a number of programs fail and display other signals as=20 well. However, in those cases, I think it definitely does NOT depend=20 on my hardware. ;-)) In fact, that hardware runs make release (!) operations, it compiles=20 megaports (which megaports take more time than make world itself),=20 and, needless to say, it performs make world operations as well. In the light of the foregoing, I don't worry at all... Just my 2 picoEuro. Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message