From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from correo.horus.es (correo.horus.es [2.139.157.236]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B7CB7E016BD for ; Mon, 7 Oct 2013 02:16:30 -0700 (PDT) Received: from [172.30.250.61] (172.30.250.61) by horus27 (Axigen) with (CAMELLIA256-SHA encrypted) ESMTPSA id 1102CF; Mon, 7 Oct 2013 11:16:26 +0200 Message-ID: <52527BEA.9090307@horus.es> Date: Mon, 07 Oct 2013 11:16:26 +0200 From: =?ISO-8859-1?Q?Jose_M=AA_Ferreiro?= User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121005 Thunderbird/16.0 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org References: In-Reply-To: X-AxigenVirus-Level: 1 X-AxigenSpam-Level: 2 Subject: Re: How to convert QA error to warning ? 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: Mon, 07 Oct 2013 09:16:31 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Otavio El 05/10/2013 20:12, Otavio Salvador escribió: > On Sat, Oct 5, 2013 at 6:12 AM, Diego Sueiro wrote: >> In recipe put the following : >> >> INSANE_SKIP_${PN} = "installed-vs-shipped" >> >> Explanation : >> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes-insane > This is a workaround and it'd be better if you guys could help fixing > this error and send the patch for meta-oe mailing list for review. > This way you also contribute back to the Yocto community. > We report on yocto mailing-list a similar error for dbus on meta-toolchain-qt image. I think the problem must be the same: something in the recipe/module source is wrong and bitbake is trying to ship the files to the host root file system instead of the directory where the image is building. The problem is that, we being a newbies with not many time, we were not able to find were the difference was with dylan-toolchain-dbus. It is working there (at last an error is not launched). We even google-found that the dbus problem was reported many time ago but we did not found the solution reported. If you can give us a tip to where look for the root the problem, we will give it another try. Thank you