From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 15611E00960; Mon, 4 May 2015 12:38:41 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id AE780E007B9 for ; Mon, 4 May 2015 12:38:32 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 5C92E600087E; Mon, 4 May 2015 22:38:30 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1430768310; bh=DYtw2J2TecybY1LbYAsWuDShJ8e8H9ubQa8iKUgwae8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=WFWL6HXjo3RoI5BXP4Xddg1PkikZPhQFmQV9d/0FQzUHYZUTXhxqkYxc1+7PZgXJ0 oQrazmrxehnMz6fQjvnqe9MP6baRGgzM/joklPeafw1ocKgiu6AROsQvzN1yBZsNab M5tfTgAa4rdD18hyVekTuMpJuXTG+FmkPT2xUd8g= Message-ID: <5547CAB6.5040706@mail.bg> Date: Mon, 04 May 2015 22:38:30 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Daiane Angolini References: <1430408987-24977-1-git-send-email-picmaster@mail.bg> <1430408987-24977-2-git-send-email-picmaster@mail.bg> <55477525.1030005@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-demos][PATCH] riotboard: Fix broken image builds against linux-fslc 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, 04 May 2015 19:38:41 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Daiane, On 05/04/2015 08:06 PM, Daiane Angolini wrote: > On Mon, May 4, 2015 at 10:33 AM, Nikolay Dimitrov > wrote: >> Hi Fabio, >> >> On 05/04/2015 03:41 PM, Fabio Estevam wrote: >>> >>> Hi Nikolay, >>> >>> On Thu, Apr 30, 2015 at 12:49 PM, Nikolay Dimitrov >>> wrote: >>> >>>> +# FIXME: Workaround for building against linux-fslc >>>> +RDEPENDS_${PN}_remove_imx6dl-riotboard = "gst-plugins-gl" >>> >>> >>> This doesn't seem to scale very well as we would need to put >>> every mx6q/dl board that uses linux-fslc in this list. >>> >>> Regards, >>> >>> Fabio Estevam >> >> >> I completely understand and agree, but I don't feel qualified to >> force all other mx6 maintainers to use the same approach. If others >> decide to go this way, we can then use the "_remove" clause for all >> "mx6" SOCs, and put appropriate comment in the file. But as of >> today, I don't see such push. > > gst-plugins-gl is included in the image by: > https://github.com/Freescale/meta-fsl-demos/blob/master/recipes-fsl/packagegroups/packagegroup-fsl-gstreamer-full.bb#L21 > > right? > > So, remove opengl from your DISTRO_FEATURES and it should work. > > > However, we have already this line: > > https://github.com/Freescale/meta-fsl-demos/blob/master/recipes-fsl/packagegroups/packagegroup-fsl-gstreamer-full.bb#L27 > > Which means mx6sl cannot handle gst-plugins-gl. Riot is not mx6sl, > so maybe you have spoted another corner case. Thanks for your comments. I've already sent an email with same analysis just before sending the patch, which uses the described above method. >> Considering the amount of discussion my patches provoke, I'm now >> more inclined to propose micro-changes that are more obvious/easier >> to approve and move forward. > > Please, keep the discussion up and running. Please, keep the > questions and the patches, we really need more experienced board > maintainers for the community boards. Regards, Nikolay