From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.free-electrons.com (top.free-electrons.com [176.31.233.9]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C46BCE015A9 for ; Sun, 22 Sep 2013 03:48:59 -0700 (PDT) Received: by mail.free-electrons.com (Postfix, from userid 106) id AE0C78DB; Sun, 22 Sep 2013 12:49:02 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.free-electrons.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.3.2 Received: from [192.168.1.55] (128-79-216-144.hfc.dyn.abo.bbox.fr [128.79.216.144]) by mail.free-electrons.com (Postfix) with ESMTPSA id 6221A60B; Sun, 22 Sep 2013 12:49:02 +0200 (CEST) Message-ID: <523ECB17.5010103@free-electrons.com> Date: Sun, 22 Sep 2013 12:48:55 +0200 From: Alexandre Belloni Organization: Free Electrons User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Otavio Salvador References: <52386630.2080207@free-electrons.com> <523D4F5F.4060208@free-electrons.com> In-Reply-To: X-Enigmail-Version: 1.5.2 Cc: "meta-freescale@yoctoproject.org" Subject: Re: imx-bootlets build failure X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 10:49:02 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 21/09/2013 23:37, Otavio Salvador wrote: > On Sat, Sep 21, 2013 at 4:48 AM, Alexandre Belloni > wrote: >> On 17/09/2013 16:38, Otavio Salvador wrote: >>> Yes, this is weird indeed. >>> >>> This has been done using my autobuilder and it helps to spot some >>> miss-use or weird things like that. >>> >>> So it uses same tmp directory for all builds and it helps to spot some >>> inter-machine dependencies and wrong settings. I still not clear what >>> might be causing this yet. >>> >> Ok, so I can reproduce it, using the following steps: >> >> MACHINE=cfa10036 . ./setup-environment build >> bitbake core-image-minimal >> rm -rf tmp/ >> cd .. >> mv build/ build1 >> . ./setup-environment build1/ >> bitbake core-image-minimal > I am attaching the patch that fixes the issue for me. Can you give it a try? > Working fine on my side ! -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com