From owner-freebsd-bugs@FreeBSD.ORG Mon Oct 27 10:17:04 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A070E16A4B3 for ; Mon, 27 Oct 2003 10:17:04 -0800 (PST) Received: from smithers.nildram.co.uk (smithers.nildram.co.uk [195.112.4.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF57D43FAF for ; Mon, 27 Oct 2003 10:17:03 -0800 (PST) (envelope-from nullentropy@lineone.net) Received: from lineone.net (orbital.gotadsl.co.uk [81.6.215.230]) by smithers.nildram.co.uk (Postfix) with ESMTP id 3E7E12724FF; Mon, 27 Oct 2003 18:16:51 +0000 (GMT) Message-ID: <3F9D6112.5060600@lineone.net> Date: Mon, 27 Oct 2003 18:16:50 +0000 From: Robert Downes User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: ar, es, fr, en, en-us MIME-Version: 1.0 To: "Christoph P. Kukulies" , freebsd-bugs@freebsd.org References: <3F9C85EF.1010207@lineone.net> <20031027072518.GA40237@gilberto.physik.rwth-aachen.de> In-Reply-To: <20031027072518.GA40237@gilberto.physik.rwth-aachen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: make buildworld fails (and asks for a bug report to be made) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2003 18:17:04 -0000 Christoph P. Kukulies wrote: >On Mon, Oct 27, 2003 at 02:41:51AM +0000, Robert Downes wrote: > > >>make -j4 buildworld fails, and I spotted the following within, several >> >> > > >Are you sure it is the -j4 that is causing the segfault? >Is it repeatable? Does it fail always at the same point? > >I had segfaults and ill insts some time agao and it turned out that >it was hardware (memory). > > Well, I just regathered the sources and `make buildworld` worked all the way through. Possibly the sources I was trying to compile last night had a minor problem (I saw another person complain about a very similar problem when they were using -j16), or maybe my machine can't handle -j4 because it's only an Intel Celeron. -- Bob