From owner-freebsd-ppc@FreeBSD.ORG Sat May 31 15:29:31 2014 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D303BEC6 for ; Sat, 31 May 2014 15:29:31 +0000 (UTC) Received: from i3mail.icecube.wisc.edu (i3mail.icecube.wisc.edu [128.104.255.23]) by mx1.freebsd.org (Postfix) with ESMTP id A6E6421EB for ; Sat, 31 May 2014 15:29:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by i3mail.icecube.wisc.edu (Postfix) with ESMTP id DD66D38067 for ; Sat, 31 May 2014 10:29:24 -0500 (CDT) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from i3mail.icecube.wisc.edu ([127.0.0.1]) by localhost (i3mail.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id qAZiv9tYVG1R for ; Sat, 31 May 2014 10:29:24 -0500 (CDT) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) by i3mail.icecube.wisc.edu (Postfix) with ESMTPSA id 951F43805E for ; Sat, 31 May 2014 10:29:24 -0500 (CDT) Message-ID: <5389F553.80302@freebsd.org> Date: Sat, 31 May 2014 08:29:23 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Subject: Re: Odd failures during parallel PPC builds References: <5388B184.4050309@freebsd.org> <538992B4.8030209@gmail.com> In-Reply-To: <538992B4.8030209@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 May 2014 15:29:31 -0000 Have you tried with HEAD? I'm doing that routinely and it works fine. How many/which CPUs are in your machine? How much RAM? -Nathan On 05/31/14 01:28, Jukka Ukkonen wrote: > Hi all, > > I sent the question below to Peter Grehan a few days ago. > He told me that he has not seen the symptoms I had found > possibly because he does ppc cross-builds on amd64. > I have tried to maintain my amd64, ppc, and sparc64 systems > as independent as possible. Usually I cross-build only my > R-PI on amd64. > Now it seems I have found something going wrong with > parallel make on ppc such that the same symptoms cannot > be reproduced on an amd64 platform. > >> I just wonder am I the only one to see odd failures during >> parallel builds on a 32-bit ppc system with "make -j #" in >> which # >= 2. Has anyone else noticed similar symptoms? >> The make version is apparently bmake. The OS version I have >> used is 10-stable. >> When I use the traditional 1 process at a time approach >> with PPC builds everything comes out just fine, though, >> about 1,5 times slower on a 2 core system. >> >> On a 12 core amd64 "make -j 60" is just fine, but on >> a 2 core ppc "make -j 2" often seems to be too much. >> I have no idea of the root cause yet. I am just confused. >> This has anyhow been going on for a few weeks now. So, I >> assume someone else might have already noticed something >> similar. >> Typically the error codes during parallel builds have been >> ENOENT and EINVAL during the last few weeks. The failure >> does not happen always at the same time, nor is the error >> code always the same. >> >> Are there maybe known conditions like configuration >> settings or something which could cause these odd failed >> parallel builds on a ppc system? > Is there anyone else trying to run local builds on > 32-bit ppc? If so, have you noticed any problems with > parallel make? Is there any other way to work around > this problem but avoiding the parallel builds completely? > > BR, > --jau > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >