From owner-freebsd-ppc@FreeBSD.ORG Sat May 31 08:28:41 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 646CEA50 for ; Sat, 31 May 2014 08:28:41 +0000 (UTC) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFB6A2379 for ; Sat, 31 May 2014 08:28:40 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id bs8so2267314wib.12 for ; Sat, 31 May 2014 01:28:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=COBOIvrm1WgCTJCMqX40t3n+Yp2lpRnT0EfCdZs8geQ=; b=GLBQxHAwPq1MbcWbG29MXXZs3VtEMdqQOvnpoq6wPjx7QHViR33DOaIvoGxoIgsi1S cDh5FA0m1tLv/pDFc2no2oSo96uH3AS4qzlqdyfEJrkip5T/LuT6EU2XV1BEbMkZ3P0+ uWVL3CYfnVTgKq4klp+1/qnYHNGT0pDRU2VBcL14Ibff+syXaycgDck+4bgJvnlssYpk WMp4Ree7Yk/Lp8SEQKwYWmG0/UcUF9dTuqQoipTx+iW9VOMeWalE3FEuz8R1WC0jZcEG AtCnlpA/XMuyTHIA8YA6Q+9XrcBDXFO4knWiBBmLa382UC20O3lmAFzy+t8lJu3K7wYG SH1w== X-Received: by 10.195.18.8 with SMTP id gi8mr30458369wjd.75.1401524919249; Sat, 31 May 2014 01:28:39 -0700 (PDT) Received: from [192.168.1.131] (xdsl-205-163.nblnetworks.fi. [83.145.205.163]) by mx.google.com with ESMTPSA id l4sm12909182wiy.0.2014.05.31.01.28.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 May 2014 01:28:38 -0700 (PDT) Message-ID: <538992B4.8030209@gmail.com> Date: Sat, 31 May 2014 11:28:36 +0300 From: Jukka Ukkonen 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: Odd failures during parallel PPC builds References: <5388B184.4050309@freebsd.org> In-Reply-To: <5388B184.4050309@freebsd.org> X-Enigmail-Version: 1.6 X-Forwarded-Message-Id: <5388B184.4050309@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 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 08:28:41 -0000 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